Why Subversion over Visual Source Safe?
While Visual Source Safe (VSS) is fully integrated into the Visual Studio environment, there are many disadvantages that can not be ignored. Reliability Sam Gentile, in his blog post entitled “No More VSS, Its Subversion”, is so bold to just link to the search terms “VSS+corrupt” on Google to make a case for the ubiquity of VSS problems. • Numerous accounts of crashing and corruption: See links above… • Not a client-server application: The current VSS setup makes it difficult to expose source code to developer’s outside your network. • Database size restriction: Some say the limit is 2GB, others say 10GB. Even if it’s 100GB – who want’s to worry about a size restriction? Preferential Issues There are also a number of issues with VSS that are most fairly described as “preferential issues”. I cite these issues because while they are not technically “bugs” they do represent limitations that many developers find as a hurdle to deal with in the real world. Examples of some of these issues
