For the the last few years I’ve worked with Visual SourceSafe (VSS), Vault, StarTeam, and Subversion. For me, the easiest and most straight forward is Subversion (SVN). Don’t get me wrong, if you come from VSS there is a mind shift to how SVN works but it is well worth it. After I started my last job and I saw that we still used VSS I immediately started pushing for the change to anything but VSS.
This week I got the approval to start migrating all of our source from VSS over to SVN. There is a great tool to help with that called VSSMigrate. Reading through the comments I found that Tim Erickson had created a new version written in C# using SharpSVN (10/22/2008 comment). Sweet Action!
The tool is really good and does an excellent job. After running the migration I realized that all of the VSS bindings are still in the project/solution files and that the VSS "*scc" files were in SVN. I used this codeproject article as the basis for the functionality I added that removes all of the VSS binding information and doesn't import any of the *scc" files.
I emailed the guys at PowerAdmin and the original author but in the event that it doesn’t get posted anywhere I wanted to make it available.
[update this project is now on Codeplex. Please post issues or comments there. Thanks!]
VssMigrate.Tim2.zip (8.95 mb)
[update: after Dan's comment here is an x86 version that should work on 64 bit systems]
VssMigrate.Tim2(x86).zip (8.95 mb)