by
Bobby Cannon
July 01, 2010 10:57 PM
I wanted to document my issues with source control and maybe it will help someone out there. I have been using Microsoft Sourcesafe for many years. I've never been particularly happy with VSS but what else integrates into Visual Studios? Well I found SourceGear Vault. The server installation was so easy. The client even easier. So much that there is really no need to comment on how or what should be done. SourceGear has great installation instruction right on their website.
My next step was to move my current Visual SourceSafe database to the new SourceGear Vault. This step really concerned me until I noticed that in the downloads they had a migration tool. Now the first thought is yeah right like that will work. I must apologize to SourceGear. The migration tool work perfectly. It was absolutely perfect.
Next I decided to open a project and see if I could just pick up a project and get to work. Here is the temporary road block. I received the following error message. The project is still bound to SourceSafe. I had to figure out how to get the bind to Vault instead. Make sure you have gotten the latest version of the project. Open the project and select the "remove bindings" option on the next dialog after the warning. VS has selected VSS as the current plug-in so you have to go back into the VS options and reselect SourceGear Vault for the source control plug-in. Once you have reestablished the correct plug-in you can rebind the project to Vault. Click File->Vault Source Control->Change Vault Bindings. After binding you are ready to go!
If you are a neat freak like me you can go and remove the .vssscc and .vspscc files from the solution and projects.