Some paths that are not valid cannot be migrated from Visual SourceSafe to Visual Studio Team Foundation Server

Article translations Article translations
Article ID: 951195 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you migrate from Microsoft Visual SourceSafe (VSS) to Microsoft Visual Studio 2008 Team Foundation Server or to Microsoft Visual Studio 2005 Team Foundation Server, some paths that are not valid cannot be migrated. For example, when you use the VSS Converter to perform the migration, you may encounter one of the following issues:
  • If the history of an item contains an action for a path that is not valid, the action is not migrated. For example, if you previously added or renamed a path that is not valid, the action is not migrated.
  • If the current item has a path that is not valid, a nonfatal error occurs on the server. Then, the VSS Converter cannot check in the path in Visual Studio Team Foundation Server.
Additionally, if you use the analyze command in the VSS Converter, all the items that contain a Visual Studio Team Foundation Server path that is not valid are logged in the migration report.

CAUSE

This issue occurs because the path restrictions in Visual Studio Team Foundation Server are more restrictive than the path restrictions in VSS. Therefore, some paths that exist in VSS cannot be used in Visual Studio Team Foundation Server.

Typically, this issue occurs for one of the following reasons:
  • The path contains a Visual Studio Team Foundation Server reserved name.
  • The path contains a file name that is in the MS-DOS-compatible short name format. For example, the path contains the following file name:
    Abcdef~1.txt
    Note Visual Studio 2005 Team Foundation Server allows the MS-DOS-compatible short name format. By default, Visual Server 2008 Team Foundation Server does not allow the MS-DOS-compatible short name format. Therefore, you encounter this issue only when you migrate to Visual Studio 2008 Team Foundation Server. For more information about why Visual Server 2008 Team Foundation Server does not allow the MS-DOS-compatible short name format, click the following article number to view the article in the Microsoft Knowledge Base:
    947649 Team Foundation Server Source Control Explorer may incorrectly download files with ambiguous short names

RESOLUTION

To resolve this issue, use one of the following methods.

Method 1: The path contains a Visual Studio Team Foundation Server reserved name

Change the path in VSS, and then migrate the item again.

Method 2: The path contains a file name that is in the MS-DOS-compatible short name format

Enable a feature on the Application Tier server that makes Visual Server 2008 Team Foundation Server allow the MS-DOS-compatible short name format. To do this, follow these steps:
  1. Make sure that you have Visual Studio 2008 Team Foundation Server Service Pack 1 installed.
  2. On the Application Tier server, locate the following folder:
    Installation folder\web services\version control
    Note Installation folder is a placeholder for the actual installation folder for Visual Studio 2008 Team Foundation Server.
  3. In Notepad, open the Web.config file.
  4. Under the <configuration> element, locate the <appSettings> element, and then add the following element.
    <add key="allow8Dot3Paths" value="true" />
    For example, update the code as follows.
    <configuration>
    ...
        <appSettings>
    ...
            <add key="allow8Dot3Paths" value="true" />
    ...
        </appSettings>
    ...
    </configuration>
    
  5. Save the Web.config file.
  6. Perform the migration.
  7. Change all the paths that use the MS-DOS-compatible short name format to use the long name format.
  8. In the Web.config file, locate the following element.
    <add key="allow8Dot3Paths" value="true" />
  9. Change the element in step 8 to the following element.
    <add key="allow8Dot3Paths" value="false" />
  10. Save the Web.config file.
Note Enable this feature only when you perform the migration. If you enable this feature during typical use of Visual Studio 2008 Team Foundation Server, you may encounter file name collisions between the MS-DOS-compatible short name format and the long name format.

MORE INFORMATION

For more information about Visual Studio Team Foundation Server reserved names, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa980550.aspx

Properties

Article ID: 951195 - Last Review: June 4, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft Visual Studio 2005 Team Foundation Server
  • Microsoft Visual Studio Team System 2008 Team Foundation Server
  • Microsoft Visual SourceSafe 2005 Standard Edition
Keywords: 
kbexpertiseadvanced kbtshoot kbprb KB951195

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com