How to: Migrate Source Control Bindings from Visual SourceSafe
For Visual Studio 2005 and Visual Studio 2008 solutions, the VSS converter will automatically migrate the source control bindings to Team Foundation version control so that you can perform source control operations in Visual Studio. If for some reason a solution does not migrate correctly, you can manually migrate the source control bindings. You can use the following procedure to migrate solutions and projects that were developed in Visual Studio versions earlier than Visual Studio 2005 so that they bind to Team Foundation version control.
Required Permissions
To perform this procedure, you must be a member of the Contributors security group or have the Read, Check In, and Check Out permissions set to Allow. For more information, see Team Foundation Server Permissions.
Converting Older Projects
Use the following procedure to convert source control bindings for Visual Studio 2005 and older projects.
To convert and modify the source control bindings
If you do not have the folder mapped to your workspace, follow these steps:
In Source Control Explorer, right-click the folder containing the solution and then click Map to Local Folder.
Select an appropriate folder on your local computer and then click Map.
In the prompt asking if you want to get the files from version control, click Yes.
A copy of the folder and files is retrieved to the mapped local folder.
Right-click the folder containing the solution, and then click Check Out for Edit.
In the Check Out dialog box, click Check Out.
On the File menu, click Open, and then click Project/Solution.
In the Open Project dialog box, find and select the solution file you checked out, and then click Open.
In the Visual Studio Conversion Wizard, click Finish.
Team Foundation automatically converts the solution (.sln) and project (.proj) files to Visual Studio 2008 format. The solution is also bound to Team Foundation.
When the conversion is complete, click Close.
In Source Control Explorer, right-click the folder containing the solution and then click Check In Pending Changes.
Provide any necessary details in the Check In dialog box, select all the files, and then click Check In.
Manually Changing Source Control Bindings
Use the following procedure to manually change the source control bindings.
To manually change the source control bindings to Team Foundation Server
If you do not have the folder mapped to your workspace, follow these steps:
In Source Control Explorer, right-click the folder that contains the solution, and then click Map to Local Folder.
Select an appropriate folder on the local computer and then click Map.
In the prompt asking if you want to get the files from version control, click Yes.
A copy of the folder and files is retrieved to the mapped local folder.
Right-click the folder that contains the solution, and then click Check Out for Edit.
In the Check Out dialog box, click Check Out.
Double-click the solution file to open it in Visual Studio.
On the File menu, click Source Control, and then click Change Source Control.
The Change Source Control dialog box opens and lists each solution and project that can be rebound.
If the solution and projects are already bound to Visual SourceSafe, you must unbind them. Click Unbind.
Note
If you are prompted to confirm the unbind operation, click Unbind.
Click OK.
On the Tools menu, click Options.
Select the Source Control node.
For Current source control plug-in, select Visual Studio Team Foundation Server.
Click OK.
On the File menu, click Source Control, and then click Change Source Control.
For each row that is not bound to a server, click Bind.
Click OK.
In Source Control Explorer, right-click the folder that contains the solution, and then click Check In Pending Changes.
Provide any necessary details in the Check In dialog box, select all the files, and then click Check In.
See Also
Tasks
Walkthrough: Migrating from Visual SourceSafe to Team Foundation