Sample VSS Converter Settings File

The VSS Converter settings file is an XML file where you provide the configuration for analysis or migration. The sections in the settings file are described later in this topic, followed by a sample settings file for analysis and migration that you can use to create your settings file.

Settings File Sections

The VSS converter XML based settings file contains several sections that specify configurations that you have to provide to either analyze a Visual SourceSafe database for migration or to migrate to Team Foundation. The sections are described in more detail in this topic.

<ConverterSpecificSetting>

The <ConverterSpecificSetting> XML section contains settings information about the Visual SourceSafe database that you want to migrate. The converter uses the information for migration.

  • The name setting in the <VSSDatabase> element has the path of the folder that contains the srcsafe.ini file.

  • The name setting in the <UserMap> element contains the user mapping file. For more information, see How to: Edit the Source Control Migration User Mapping File.

  • Specify the following in the <Project> element which is under the <ProjectMap> section:

    • The Visual SourceSafe folder for analysis or migration

    • For migration, the folder to migrate to in Team Foundation source control.

    You can add multiple <Project> elements to analyze or migrate multiple Visual SourceSafe folders.

    Note

    The converter uses SQL Express during migration. If your migration fails caused by the 4GB limit of SQL Express, you can set the converter to use SQL Server instead by adding the following line to the <Source name="VSS"> section: <SQL Server="SQL_Server_name"></SQL>   

<Settings>

Under the <Settings> section, in the file setting of the <Output> element, you can specify the file name and location of the analysis or migration report. If you do not specify a file name, the converter generates the file that uses the name VSSAnalysisReport.xml during analysis and VSSMigrationReport.xml during migration.

XML Encoding

The <?xml encoding> tag must match the encoding used to save the settings.xml file. For example, if the file is saved as Unicode, the <?xml encoding> tag is:

<?xml version="1.0" encoding="unicode">

Instead of:

<?xml version="1.0" encoding="utf-8">.

Settings File Format for Analysis

The settings file contains the information the Visual SourceSafe Converter must have to analyze the Visual SourceSafe database to be migrated. You can copy the XML shown later in this topic and edit it to create your own settings file.

<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
<ConverterSpecificSetting>
     <Source name="VSS">
          <VSSDatabase name="c:\VSSDatabase"></VSSDatabase>
          <UserMap name="c:\Migrate\Usermap.xml"></UserMap>
     </Source>
     <ProjectMap>
          <Project Source="$/FolderA"></Project>
          <Project Source="$/FolderB"></Project>
     </ProjectMap>
</ConverterSpecificSetting>
<Settings>
     <Output file="Analysis.xml"></Output>
</Settings>
</SourceControlConverter>

Note

If any one of the previous sections is missing, you receive an XML validation error.

Settings File Format for Migration

The settings file contains the information the Visual SourceSafe Converter must have to migrate your Visual SourceSafe database to Team Foundation source control. You can copy the XML shown later in this topic and edit it to create your own settings file, or use the procedures earlier in this topic to change the settings file that you created for the analysis.

<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
<ConverterSpecificSetting>
     <Source name="VSS">
          <VSSDatabase name="c:\VSSDatabase"></VSSDatabase>
          <UserMap name="c:\Migrate\Usermap.xml"></UserMap>
     </Source>
     <ProjectMap>
          <Project Source="$/FolderA" Destination="$/TeamProjectA"></Project>
          <Project Source="$/FolderB" Destination ="$/TeamProjectB/ProjectB"></Project>
     </ProjectMap>
</ConverterSpecificSetting>
<Settings>
     <TeamFoundationServer name="My_TFS_Server" port="8080" protocol="http"></TeamFoundationServer>
     <Output file="Migration.xml"></Output>
</Settings>
</SourceControlConverter>

Note

If your project source is $/FolderA and your destination is $/TeamProjectB/ProjectB a Visual SourceSafe project $/FolderA/ProjectA becomes $/TeamProjectB/ProjectB/ProjectA in Team Foundation source control, instead of $/TeamProjectB/ProjectB/FolderA/ProjectA.

See Also

Tasks

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