SourceSafe or not SourceSafe

[rgh]

Currently we are using SourceSafe for source control within our VB projects, however I am finding that it does not meet our requirements. My main problem is that when a form is checked in from the SourceSafe addin I can see no way of forcing the user to enter a comment. I then need to run a report showing changes from the date of last release so that I can produce release notes for our customers.<br>
<br>
Can anyone tell me of a better source control tool, or let me know how to force the comment.<br>
<br>
Thanks.<br>
<br>
Richard.

 

[MikeLacey]

No way I know of to force the comments (that's a problem for us as well)<br>
<br>
We get around this by not allowing individuals to both check out and check in files. A programmer will check a file out and then his/her team leader will check it in.<br>
<br>
You're probably correct - there are better SCCS apps out there.<br>
<br>
Mike<br>
<p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>

 

[Tinman]

This is a problem with Source Safe... but I got stuck being a source safe admin... and I know I can go and view the version checked in and a previous version side by side it even points out the different lines of code for you... <br>
I am a vb programmer and I had terrible documentation before this... but I found it not as hard to go back and put in the comments afterwards... <p> Chad<br><a href=mailto:tinman@hotbot.com>tinman@hotbot.com</a><br><a href= > </a><br>Tinman,<br>
Welcome to OZ.

 

[jguetzlaff]

SourceSafe! it's not all that bad ...
When You check in files from the VB IDE, there is a dialog appearing, which will allow for adding a comment. Unfortunately there's only one comment possible for all files at one check in time. To force a user entering a comment, You could try writing a SourceSafe Add-In, which will capture the BeforeCheckin-Event. That's what I'm working on with SourceSafe 5.0, but can't get beyond having my Add-In registerd by SourceSafe. The MSDB docu on this subject is a mess. Maybe somebody can help!

 

[maxpower1]

You have to be proactive about it. What you can do is assign usernames and passwords for each individual. Then, when you run the report and no comments are showing up, you can pinpoint the individual that checks in/out files without writing comments.