In most cases, migration from AnkhSVN to VisualSVN is easy and hassle free. But in certain cases you may experience technical issues caused by AnkhSVN bindings in the project files of your solution. The article describes the correct steps to migrate from AnkhSVN to VisualSVN and solve any possible issues.
Perform the following steps to migrate from AnkhSVN to VisualSVN:
- Close all instances of Visual Studio.
- Uninstall AnkhSVN.
- Install VisualSVN.
- Open Windows Explorer and remove the solution user options (.suo)
file in your solution folder.
Warning The solution user options (.suo) file contains user specific settings such as location of the breakpoints. These settings be lost when you delete the .suo file.
- Start Visual Studio and open your solution.
- Visual Studio will prompt you to remove the source control bindings with the following message:
- Choose Yes and Visual Studio will clear the AnkhSVN bindings from all projects files in your solution.
- Choose VisualSVN | Commit main menu command to commit the changes made to the project files.
- Your solution will be disconnected from AnkhSVN and become handled by VisualSVN.
AnkhSVN bindings are stored directly in the project's file (e.g. *.csproj for Visual C# projects and *.vcproj for Visual C++ projects) and are also cached in the solution user options (.suo) file. For some reason these bindings lead Visual Studio to confusion when you approach to migrate to VisualSVN. The problem is indicated by one of the following warning messages:
The problem occurs for all the projects with AnkhSVN bindings and prevents these projects from being loaded (these projects become marked by "load failed" text in the Solution Explorer).