Justin J. Vogt

On one of our projects, the development team had some concerns related to a recent production deployment and the suspected culprit was in the Source Control Management (SCM) system.

For a little background, the project was started several years ago and Visual Source Safe (VSS) was used for the SCM system.  More recently, the development team moved away from VSS and onto Team Foundation Server (TFS).  For additional background, the development team kept the VSS database in tact for historical purposes.

With a little manual digging the development team proved that their suspicion was correct… one of the developers checked code into the wrong source code database.  This lead to a very uneasy feeling for the project manager, and the SCM solution was under quick scrutiny.  A few web searches and 30 minutes later I had an answer to the question… “How many other changes were checked into the VSS database?”

The following tool allowed me to run a search on all files modified and checked in by anyone after a specific date… saved the day:

http://www.codeproject.com/KB/applications/VssReporter.aspx