Over a million developers have joined DZone.

Upgrade Visual Sourcesafe to Team Foundation Server 2012

DZone's Guide to

Upgrade Visual Sourcesafe to Team Foundation Server 2012

· ·
Free Resource

In this post I will explain how to upgrade and migrate projects or repositories from VSS or Visual SourceSafe 2005 to TFS or Team Foundation Server 2012
1-Upgrade VSS Projects to TFS 2012 intro

Open Visual SourceSafe Administration. 2-Open VSS Administration

Create new Database or Repository for VSS Projects. 3-Create new DB

Click Next and select the location of the Database, I create a folder called Marvel-VSS. 4-Select location of DB

Create a project inside that Repository, it’s name will be MVCProject. 5-Add Project

Create a mapping folder on the local HDD, it’s name will be My Work. 6-Set working folder in VSS

Navigate to the folder using windows explorer and add new text file as an example of the source code of your project, I typed Hello World! inside the file.

7-Add file to the project

Add the existing source code (text file) to the VSS Repository. 8-Add file to VSS

Check-in files into the VSS.

9-Check-in files

Navigate to the second machine that has TFS 2012 and create new project, it’s name will be Marvel-TFS. 10-Create new Team Project

Download Visual Source Safe Upgrade Tool 11-Visual-SourceSafe Upgrade tool

Install the upgrade tool.

12-setup upgrade tool

Launch VSS Upgrade Tool Wizard and browse to the Marvel-VSS Repository on the VSS machine, click on List Available Projects to retrieve the project from that Repository, click on the check-box and then click Next. 13-VSS Upgrade wizard

Browse to the created project on TFS (Marvel-TFS) and select it. 14-Choose team project to migrate on

Click Next and then click on Verify after that click on Upgrade. 15-Readness Checks

Review the completion of the upgrade. 16-Success

Review the team project on TFS to make sure that the source code has been migrated successfully. 17-examin the file on the TFS


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}