Visual Studio Team Foundation Server 2010 powerful version-control features. But we already have an existing version-control facility: Visual SourceSafe.
Visual SourceSafe was very convenient for personal use. Because it is able to be installed on desktop OS.
In the other hand, current version of TFS supports client OSs with only few limitations [Fantastic!!]. Now we can use advantaged functions with TFS.
However, we have to migrate old archives from VSS to TFS. We have a tool for migration but this progress is a little bit tricky.
This article shows how to migrate archives from VSS to TFS.
This article is based on Visual Studio Team Foundation Server 2010 (30319.01.10).
Originally installed TFS needs initial settings. The [Basic Configuration Wizard] helps us to configure the basic features of TFS. This wizard can be launched by install result form or you can launch from TFS management console.
This process open the TFS main functions; source control, team query.
1Select [Basic] in left pane, click [Start Wizard].
2If you would like to feedback, Check [Yes]. Click [Next].
3Select your database setting. If you have existing instance of SQL Server, lower one. If you have no SQL Server, you can compose SQL Server Express. In this case, we choose a more complex scenario using existing SQL Server. Click [Next].
4Fill in the existing SQL Server instance name. Click [Next].
5Confirm the settings: database, web, collections, etc. Click [Next].
6At first, the validation for setting is launched. If your system passes all checks, you can click [Configure].
7Configurations will progress. After all configurations finished, click [Next].
8That's all for configuration. You can check the result.
Migration from VSS to TFS is a little bit tricky. The correct procedure is as follows.
VSSConverter is a migration tool for TFS 2010.
1Apply a patch; KB950185. 2Create a new destination [Team project]. 3Create a new VSSConverter settings.xml 4Analyze settings with VSSConverter. 5Migrate with VSSConverter.
Step by step migration
Apply a patch; KB950185
If your vss has not been applied KB950185, following alert is shown during migration.
1Download [VS80-KB947647-X86-INTL.exe] file(Why KB947647?) and double click it. And Click [OK].
2Read the EULA and choose your answer.
3The installation starts immediately.
4That's all for applying a patch.
Create a new destination [Team project].
If you have not created a destination [Team project] ([fromVSS] is a destination in this procedure), following alert is shown during migration.
1Click [Create new team project] on right click menu in VS Team Explorer, [New Team Project] dialog is launched.
Fill up team project name and description. In this procedure, the name is [fromVSS]. Click [Next].
2Select a process template you would like to use. Click [Next].
3Choose [Create an empty source control folder]. Click [Next].
4Confirm the settings. Click [Finish].
5The creation starts immediately.
6That's all for team project creation.
Create a new VSSConverter settings.xml
The following XML is a setting definition for VSSConverter. In this settings.xml, following item should be included. This settings.xml migrates all VSS source controls into [fromVSS] team protect's source control.
||Describe a VSS's ini file path.|
||Describe a SQL Server instance name. If you use SQL Server Express, this element doesn't need.|
||Describe a TFS machine name.|
||Describe an Output file path.|
01<?xml version="1.0" encoding="utf-8"?>
04 <Source name="VSS">
05 <VSSDatabase name="!!! vss data path !!!"></VSSDatabase>
06 <SQL Server="!!! SQL Server instance name !!!"></SQL>
09 <Project Source="$/" Destination="$/fromVSS"></Project>
13 <TeamFoundationServer name="!!! TFS Server name !!!"
16 collection="tfs/DefaultCollection" />
17 <Output file="!!! analysis output path !!!"></Output>
Analyze settings with VSSConverter.
VSSConverter is a command line tool. The default installation path is following;
%Program Files%Microsoft Visual Studio 10.0\Common7\IDE
To analyze the migration, you can use [analyze] option as following;
01vssconverter analyze [settings.xml path]
Migrate with VSSConverter.
After analyzing the migration, you can migrate. Commandline is following;
01vssconverter migrate [settings.xml path]
1Type [ y ] to continue.
2Type [VSS administrator password]. If you have no password, it may be [blank] (just hit [Enter]). Type [ y ] to continue.
3The migration starts immediately.
4That's all for migration. You can check analysis.xml file.
Check migrated projects.
After migration, you can get all migrated projects in destination [Team project]([fromVSS] is a destination in this procedure).