As you may know Microsoft's Visual SourceSafe is not the only well integrated and reliable source control solution. The opensource community is working with CSV, a source control system, for years already, but there's something better now. A new source control system called SubVersion derived from CSV was released and it's still free and reliable. SVN has many advantages over CVS. SVN is faster, allows for any filetype without hassle, build to last instead of another project from the attic, versioned renames, native directory support, file properties are versioned...

SubVersion for Visual Studio

So, why is this intersting to the windows (.net) developer? Well SubVersion can be integrated into Visual Studio (2003 and 2005) just as Visual SourceSafe. Just rightclick the filenames and you'll be able to commit (check in) your changes. There are three different 'plugins' available.

Ankhsv
AnkhSVN is a Visual Studio .NET addin for the Subversion version control system. It allows you to perform the most common version control operations directly from inside the VS.NET IDE. Not all the functionality provided by SVN is (yet) supported, but the majority of operations that support the daily workflow are implemented.

PushOk SubVersion SVN plugin
SVN SCC proxy is the SCC API plug-in for any Microsoft SCC enabled IDE. It is analog of well known and widly used "Pushok CVS SCC proxy" plug-in. Since SVN has much more functions than MS SCC, we integrated part of them in our plug-in.

VisualSVN
With VisualSVN you are one click away from reviewing your changes, committing them and getting other's changes. Don't worry about modification of solution or project files - VisualSVN will reload them when necessary. When you need to rename or move class, file, folder or project - just do it. VisualSVN cares about the rest.