Whats wrong with Visual SourceSafe?
For many years version control in Visual FoxPro and Visual SourceSafe were synonyms. Sessions and articles covering team development exclusively referred to Visual SourceSafe. Most commercial alternatives were designed to be used in a bigger team, not in the small teams that are so typical for Visual FoxPro. Moreover, Visual SourceSafe is a Microsoft product. As it is part of Visual Studio and because Microsoft made earlier versions available for free to conference attendees, most developers had access to Visual SourceSafe in some way. But does that mean that Visual SourceSafe is the best choice? There’s no doubt that using any version control system has many advantages. Version control systems allow multiple developers to work on the same project without having to resist to error-prone manual synchronisation of directories. They allow for documenting every change. Virtually every version control system supports labelling all files of the current version. Later you can retrieve files b
