If you are using a Source Control Management (SCM) tool
such as Rational® ClearCase®, Microsoft® Visual SourceSafe, and so on,
and want to move to Rational Team Concert™ source
control,
you must migrate the source control bindings to Rational Team Concert source
control to
perform source control operations in the Microsoft Visual Studio environment.
Before you begin
This topic does not cover migration of the source control
artifacts, which maintains file history, but instead it focuses on
migration of source control bindings. The screenshots shown display Rational ClearCase as source control bindings.
About this task
To migrate from another source control provider to
Rational Team Concert source
control:
Procedure
- Create and load a repository workspace into a file area. For more information about creating and loading a repository
workspace, see Creating a repository workspace and Loading a repository
workspace topics.
- In the Windows® explorer,
copy the solution structure from the previous provider's file
area to the root file area where you loaded the repository workspace.
- Remove the read-only attribute for the entire folder structure.
To remove read-only attribute, right-click the root folder and click Properties;
and then clear Read-only.
- Remove the source control bindings from the solution and
project files. To remove the source control bindings, open each solution
and project files and delete the text mentioning the source control
provider name.
Figure 1. Sample solution file with Rational ClearCase source control binding

Figure 2. Sample project file with Rational ClearCase source
control binding

Note: In
addition to changing SCM, if you are also upgrading to the newer version
of Microsoft Visual Studio,
for example, the projects that you are trying to migrate were created
in Microsoft Visual Studio
2005 or earlier, and your current source control provider is not available
in the version of Visual Studio that you want to use with
Rational Team Concert source
control,
the upgrade will not proceed until you complete step 4. You will see
the following error:

- After removing the existing source control bindings, open
the solution again and share it. For more information about
adding solution, see Adding solution to the repository.
Tip: While
sharing the solution, you can add rules to ignore files that remain
from the previous source control provider.
What to do next
Now, you can deliver the solution to the repository.