After Migrating Source Control
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer

After Migrating Source Control

After migrating source control successfully, you should verify that the sources have been migrated to Team Foundation version control. After migration, there are several activities you may have to perform to follow up on the migration process. You must verify that file versions were migrated correctly. You must migrate source control bindings of Visual Studio projects. You may also need to troubleshoot any problems that were reported.

NoteNote:

You always find some extra files on the Visual SourceSafe side with the extension *.scc. These files are temporary files generated by Visual SourceSafe in your local folder when you use a get command for the latest in Visual SourceSafe. The extra files are not source files.

Version Matching

Describes how VSS Converter handles potential version mismatches during the final phase of the migration process.

How to: Migrate Source Control Bindings from Visual SourceSafe

Describes how to migrate source control bindings in Visual Studio from Visual SourceSafe to Team Foundation version control.

Interpreting the Source Control Migration Report

Contains information about the messages you might see in your migration report.

Troubleshooting Source Control Migration

Contains topics that help you troubleshoot problems with migration.

Show:
© 2016 Microsoft