通过

Changing Source Control Binding

  • 项目

After migrating sources from VSS to Team Foundation using VSSConverter, here are the steps to change the source control binding of the solution files from VSS to Team Foundation. This blog talks about changing the source control binding for both VS 2003 and VS 2005 solution files.

Scenario 1:

You have done migration of your sources in VSS with solution file, which is in VS 2003 format, bound to VSS to Team Foundation.

1) Open Source control explorer.

2) Navigate to top level folder of migrated solution.

3) Right click on migrated folder and do a get of latest version. (If you haven’t used Source control on this client machine before, you will be prompted to select the local folder for default workspace mapping. Please select a suitable local folder in this case.)

4) Select the same top level folder again and do a check out for Edit. Select the default options.

5) Select the solution file on SCC and double click on that. You will get a “Source Control” message box saying,

The solution appears to be under source control, but its binding information cannot be found. It is possible that the MSSCCPRJ.SCC file or another item that holds the source control settings for the solution, has been deleted. Because it is not possible to recover this missing information automatically, the projects whose bindings are missing will be treated as not under source control.

          Click Ok.

6) Now a Visual Studio 2005 Conversion wizard will start to convert the solution from VS 2003 to VS2005. Select the default option. Solution should be converter successfully. Now do a checkin for whole solution by selecting the solution in Solution Explorer. You may have to select the solution file explicitly in Checkin window.

7) Now it is time to change the source control bindings. Select the solution file and go to File -> Source Control -> Change SourceControl. Select the solution and click on Bind. This step will bound solution file to TF. Click on Ok. You will be prompted for a checkout. Keep the defaults and do a checkout. Now your solution is bound to TF. Do a checkin and you are done.

Scenario 2:

You have done migration of your sources in VSS with solution file, which is in VS 2005 format, bound to VSS to Team Foundation. In this case VSS is not installed on your machine.

1) Open Source control explorer.

2) Navigate to top level folder of migrated solution.

3) Right click on folder and do a get latest version. (If you haven’t used Source control on this client machine before, you will be prompted to select the local folder for default workspace mapping. Please select a suitable local folder in this case.)

4) Select the same top level folder again and do a check out for Edit. Select the default options.

5) Select the solution file on SCC and double click on that. You will get a “Source Control – unable to access Database message box” saying

“The associated source control plugin is not installed or couldnot be found.” This comes because VSS is not installed on this client machine. It will also ask you to select one of the following options.

Temporarily work uncontrolled.

Permanently remove Source control association bindings.

Select the second option to remove the source control bindings and click Ok.

6) Select Tools -> Options -> SourceControl and select the Visual Studio Team Foundation plugin and click Ok.

7) Select solution node and click File -> SourceControl -> Change source control. Select the solution and project and click on Bind. Click Ok. Your solution and project will be automatically checked out. Now select the solution and do a checkin and you are done.

Scenario 3:

Same as above scenario the only difference is VSS is installed on your machine.

1) Open Source control explorer.

2) Navigate to top level folder of migrated solution.

3) Right click on folder and do a get latest version. (If you haven’t used Source control on this client machine before, you will be prompted to select the local folder for default workspace mapping. Please select a suitable local folder in this case.)

4) Select the solution file on SCC and double click on that. You will get a “Source Control” message box saying,

The solution appears to be under source control, but its binding information cannot be found. It is possible that the MSSCCPRJ.SCC file or another item that holds the source control settings for the solution, has been deleted. Because it is not possible to recover this missing information automatically, the projects whose bindings are missing will be treated as not under source control. Click Ok.

5)  You will get a “Source Control – unable to access Database message box” saying

“The associated source control plugin is not installed or could not be found.”

It will also ask you to select one of the following options.

Temporarily work uncontrolled.

Permanently remove Source control association bindings.

Select the second option to remove the source control bindings and click Ok.

6) Select Tools -> Options -> SourceControl and select the Visual Studio Team Foundation plugin and click Ok.

7) Select solution node and click File -> SourceControl -> Change source control. Select the solution and project and click on Bind. Click Ok. You will be prompted for checkout of solution and project files. Do the same with default options. Now select the solution and do a checkin and you are done.

Comments

  • Anonymous
    February 21, 2006
    The comment has been removed

  • Anonymous
    December 19, 2006
    Now, we have power toy to do this. Check out brian's blog.

  • Anonymous
    March 12, 2008
    VSS to TFS migration - a start

  • Anonymous
    March 12, 2008
    VSS to TFS migration - a start