Using UNC Paths in Visual SourceSafe

 Last reviewed: January 15, 1997
Article ID: Q138296
The information in this article applies to:
  • Microsoft Visual SourceSafe versions 4.0, 5.0

SUMMARY

Previous versions of SourceSafe could not use universal naming convention (UNC) paths. Visual SourceSafe now allows the user to use UNC paths in most SourceSafe Explorer, SRCSAFE.INI or SS.INI settings. This eliminates the need to map a drive to run SourceSafe and allows the administrator to easily place the Visual SourceSafe database on a different network server without any end-user intervention.

MORE INFORMATION

UNC paths may be used in many locations, but not every location in Visual SourceSafe. The following list contains the files, environment variables, and .INI file variables that accept UNC paths:

  • SSDIR environment variable.
  • SSINI environment variable.
  • #INCLUDE in the SRCSAFE.INI file. For more information about possible problems with using the #INCLUDE option, please see the following article in the Microsoft Knowledge Base:

    ARTICLE-ID: Q136401 

       TITLE     : Visual SourceSafe "Invalid Data Path" Error
  • SRCSAFE.INI variables:

    Data_Path Journal_File Shadow Temp_Path Users_Txt

  • SS.INI variables:

    Comment_Editor Comment_Template Editor File extension masks

Visual SourceSafe cannot use UNC paths in the following situations:
  • Working directories.
  • File dialog boxes:

    Add file Get Checkout Checkin

NOTE: These situations do not apply to Visual SourceSafe 5.0. You can use a UNC name anywhere you can supply a pathname.

REFERENCES

Query using the UNC keyword in Visual SourceSafe Books Online.

KBCategory: kbusage
KBSubcategory: SourceSafe
Additional reference words: 4.00 5.00 vss vbwin Windows 95

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.