Migrating from VSS 2005 to TFS 2010 using VSSConverter -- Missing Instructions

Published on
15,538 Points
1 Endorsement
Last Modified:
Community Pick
Megan Brooks
Retired SQL Server database developer and administrator; active MS SQL Server consultant for T-SQL, SSRS, and SSIS
If you have have been using Visual Studio 2008 with VSS and are now migrating to Visual Studio 2010 and Team Foundation Server, you may need to migrate your VSS data to TFS.  Microsoft has made VS 2010 TFS available to VS2008 with MSDN subscribers and advised that TFS is the replacement for VSS.  There is a TFS "basic" configuration that is suitable for use by individuals and small teams that do not need all the features of TFS 2010, and TFS performance can be much better than VSS, so this is a good thing.

The problem I ran into is that I couldn't find complete instructions about how to do the migration.  It turned out that all of the instructions I found by searching were for earlier versions of TFS.  I used this article:

      Walkthrough: Migrating from Visual SourceSafe to Team Foundation

which is apparently for the original TFS (2005) release.

Actually, the instructions seem to be fine except for one small detail -- when you add the <Settings> element to ConversionSettings.xml there is one additional (and seemingly undocumented) attribute that TFS requres. The old format was

    <TeamFoundationServer name="server_name" port="port_number" protocol="protocol"></TeamFoundationServer>

The new (and correct) format is:

    <TeamFoundationServer name="server_name" port="port_number" protocol="protocol" collection="virtual_root/collection_name"></TeamFoundationServer>

By default the virtual_root/collection_name would be "tfs/DefaultCollection".  Once I added that attribute, everything else went well. My final <Settings> element looked like

    <TeamFoundationServer name="server_name" port="8080" protocol="http" collection="tfs/DefaultCollection"></TeamFoundationServer>

Open in new window

One other thing that was documented (sort of) but that I overlooked is that while the instructions seemed to say that you need to install SQL Server Express before running the conversion, apparently you actually can use SQL Server instead.  Reading all of the instructions will save you that extra work. This article shows how to do it:

    How to: Create a Settings File for Source Control Analysis and Migration

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Join & Write a Comment

When you have multiple client accounts to manage, it often feels like there aren’t enough hours in the day. With too many applications to juggle, you can’t focus on your clients, much less your growing to-do list. But that doesn’t have to be the cas…
Discover the basics of using Outlook 2016 from office 365.

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month