Last version OF VSS was in 2005 and Microsoft Recommend moving to TFS Version Control and you still use VSS ...I can't believe that !!!!

VisualSVN is simply a front-end for the command line Subversion functions, just like TortoiseSVN. The difference between the two is that TortoiseSVN is a “add-in” for Windows and VisualSVN is an add-in for Visual Studio.

Ben Collins-Sussman, one of the original designers and developers of Subversion, discusses the challenge to keep Subversion simple yet practical.

"Source control is the very bedrock of software development. Without some sort of version control system in place, you can't reasonably call yourself a software engineer. If you're using a source control system of any kind, you're versioning files almost by definition. The concept of versioning...

A good, "highly visual" overview of Version Control, (a.k.a. Source Control). It also references Subversion command line examples, but the overview applies to most version control systems.

A quick walkthrough of setting up and configuring SubVersion with Tortoise SVN and getting started creating repositories, adding files and folders, creating local copies and working with SVN.

Source code control is not just a fancy version of File -> Save...

VisualSVN takes a novel approach to bringing SVN into the Visual Studio IDE... it brings Tortoise into the IDE! Rather than switching to a Windows Explorer window to use Tortoise on your source tree, VisualSVN simply opens the appropriate Tortoise screen as a modal window over Visual Studio.

VSoft, the makers of FinalBuilder, just published the results of their annual customer survey. One of the questions is which version control systems do you currently use, or plan to use, in the next 12 months? The top 9 responses are reprinted here. I'm disheartened to see that Visual SourceSafe is ...