Why Switch From Visual SourceSafe?
• SubVersion does not bind itself to Visual Studio solutions and project files. SourceSafe binds itself to VS solution and project files. Consequently, • SourceSafe bindings can cause Visual Studio to take a long time to load a project • If you are working away from the network, Visual Studio still attempts to log you into the SourceSafe database. Worst of all, it repeats this for each project in your solution or workspace; if you have two dozen projects in a workspace, you will get prompted to login 24 times. • If you distribute a library with sample projects to customers, it is very easy to forget to remove the SourceSafe bindings, and all of a sudden your customers are requested to log into your SourceSafe database. • SourceSafe does not support atomic operations. If an operation fails when checking in multiple changes, some sources will be checked in and others will not. This can cause builds to fail and documents to not agree with eachother. While the checked-in files can be rever
