"An alternative to VSS" was the requirement. Decided to plunge into CVS. SA had the CVS server installed on a Linux machine. My task was to find and explore the various CVS clients for Windows.

First, tried WinCVS. Then went on to look for CVS plugins for VS.NET. Found Jalindi Igloo. Igloo was a major failure inspite of a detailed article on the CodeProject.

Then looked into the TortoiseCVS. Inspiring integration with the windows shell. The ease of use was spell bounding. The help accompanying installation gave a detailed look into the two different methodologies for SourceControl namely, Lock-Modify-Unlock and Copy-Modify-Merge. TortoiseCVS uses C-M-M model.

A VS.NET plugin for TortoiseCVS was under development. I tried it but failed to Check out a module.

Then looked into the
SubVersion alternative for CVS. Even this follows C-M-M model. But, the VS.NET plugin developed for SubVersion, ankhsvn looks good by seing the Screen Shots. Got to install svn soon and try it. The free book on subversion is excellent.

Then went on to read the Microsoft's “Team Development Guide” from
Patterns&Practices. This guide is indispensible for VSS and VS.NET users.

Another Microsoft Article from MSDN was very good. This is related to SourceControl and build control for Web Projects.

For now, using WinCVS and TortoiseCVS together.

Waiting for something to happen.........