TimberLandChapel's Tech Blog

TimberLandChapel provide Tips, tech note and scribbling.
Updated my site as English site for APAC users.
TLC.com .Metrix 4.0 Beta1 released






SQL Server




Migration from Visual SourceSafe 2005 to Visual Studio Team Foundation Server 2010
Related Resources
Visual Studio Team Foundation Server 2010
Upgrade Visual SourceSafe 2005 to Visual Studio Team Foundation Server 2010
Scenarios and objectives

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).

Instration of TFS

If you would like to review installation notes, a link is below.

Visual Studio Team Foundation Server 2010 Installation notes
Configuration and initial setings for TFS

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]. basic wizard

2If you would like to feedback, Check [Yes]. Click [Next]. feedback

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]. database setting

4Fill in the existing SQL Server instance name. Click [Next]. database instance

5Confirm the settings: database, web, collections, etc. Click [Next]. confirm

6At first, the validation for setting is launched. If your system passes all checks, you can click [Configure]. validation progress validation result

7Configurations will progress. After all configurations finished, click [Next]. config progress config result

8That's all for configuration. You can check the result. result

Migration from VSS to TFS

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

http://code.msdn.microsoft.com/KB950185/Wiki/View.aspx http://code.msdn.microsoft.com/KB950185/Release/ProjectReleases.aspx?ReleaseId=1123

If your vss has not been applied KB950185, following alert is shown during migration. KB950185 alert

1Download [VS80-KB947647-X86-INTL.exe] file(Why KB947647?) and double click it. And Click [OK]. KB950185 welcome

2Read the EULA and choose your answer. KB950185 EULA

3The installation starts immediately. KB950185 progress

4That's all for applying a patch. KB950185 result

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. destination lost

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]. destination create

2Select a process template you would like to use. Click [Next]. destination template

3Choose [Create an empty source control folder]. Click [Next]. destination folder

4Confirm the settings. Click [Finish]. destination folder

5The creation starts immediately. destination progress

6That's all for team project creation. destination result

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.

item description
VSSDatabase.name Describe a VSS's ini file path.
SQL Server Describe a SQL Server instance name. If you use SQL Server Express, this element doesn't need.
TeamFoundationServer.name Describe a TFS machine name.
Output.file Describe an Output file path.
Code Copy to clipboard
01<?xml version="1.0" encoding="utf-8"?>
03    <ConverterSpecificSetting>
04        <Source name="VSS">
05            <VSSDatabase name="!!! vss data path !!!"></VSSDatabase>
06            <SQL Server="!!! SQL Server instance name !!!"></SQL>
07        </Source>
08        <ProjectMap>
09            <Project Source="$/" Destination="$/fromVSS"></Project>
10        </ProjectMap>
11    </ConverterSpecificSetting>
12    <Settings>
13        <TeamFoundationServer name="!!! TFS Server name !!!"
14            port="8080"
15            protocol="http"
16            collection="tfs/DefaultCollection" />
17        <Output file="!!! analysis output path !!!"></Output>
18    </Settings>
See also

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;

Code Copy to clipboard
01vssconverter analyze [settings.xml path]

Migrate with VSSConverter.

After analyzing the migration, you can migrate. Commandline is following;

Code Copy to clipboard
01vssconverter migrate [settings.xml path]

1Type [ y ] to continue. migration start

2Type [VSS administrator password]. If you have no password, it may be [blank] (just hit [Enter]). Type [ y ] to continue. migration password

3The migration starts immediately. migration progress

4That's all for migration. You can check analysis.xml file. migration result

Check migrated projects.

After migration, you can get all migrated projects in destination [Team project]([fromVSS] is a destination in this procedure). migration result

For more informations

<?xml version="1.0" encoding="utf-8"?>\n<SourceControlConverter>\n\t<ConverterSpecificSetting>\n\t\t<Source name="VSS">\n\t\t\t<VSSDatabase name="!path!"></VSSDatabase>\n\t\t\t <SQL Server="!SQL Server!"></SQL>\n\t\t</Source>\n\t\t<ProjectMap>\n\t\t\t<Project Source="$/" Destination="$/fromVSS"></Project>\n\t\t</ProjectMap>\n\t</ConverterSpecificSetting>\n\t<Settings>\n\t\t<TeamFoundationServer name="!TFS!"\n\t\t\tport="8090"\n\t\t\tprotocol="http"\n\t\t\tcollection="tfs/DefaultCollection" />\n\t\t<Output file="!path!"></Output>\n\t</Settings>\n</SourceControlConverter>

Published 2011年3月5日 0:33 by timberlandchapel


No Comments