Monitoring Visual Sourcesafe

Everybody knows Visual SourceSafe just sucks. But still a lot of people are using it. So are we.

We experienced following recently (it’s really the basic “stepping on each-others toes” scenario):

  • Someone (Person1) did a “Get Latest” and got the most recent code on his machine.
  • Another developer (Person2) also did a “Get Latest” and got the most recent code on his machine.
  • Now, Person2 checks out the code and starts editing it, and when finished checks in his changes.
  • Then Person1 starts making changes after checking out the code. However, because he didn’t do another “Get Latest”, he doesn’t have the most recent code. When he now checks his changes back in, the changes from Person2 are lost.

I then went searching for a tool to monitor SourceSafe for certain events like checking in files. On “The Code Project” I found the following tool:

SSMonitor – Monitor a Visual SourceSafe database using VBScript

After installing it as a service on each developer machine and configuring it for monitoring “Check-In” we get an e-mail when someone checks-in his changes. Great tool! Thanks Doug. Thanks Codeproject.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s