This page contains descriptions of the fields and options available when setting up VCS roots using Visual SourceSafe:
 | Notes and Limitations
- TeamCity supports Microsoft Visual SourceSafe 6.0 and 2005 (English versions only!).
- Microsoft Visual SourceSafe only works if the TeamCity server is installed on a computer running a Windows® operating system.
- Make sure the TeamCity server process is run by a user that has permission to access the VSS databases.
TeamCity has the following limitations with Visual SourceSafe:
- Shared (not branched) files cannot be checked out.
- Comments for add and delete operations for file and directories are not shown in VSS 6.0. All such operations will have "No Comment" instead of a real VSS comment. (This limitation is imposed by the VSS API, which makes it impossible to retrieve comments with acceptable performance).
|
VSS Settings
Option
|
Description
|
Path to srcsafe.ini |
The full path of the VSS configuration file srcsafe.ini of the project repository. If the TeamCity server is run as a Windows service, make sure this path does not use mapped drives. If the file is placed on a network drive use syntax like \\vss-server\share\srcsafe.ini where vss-server is a server name and share is a name of the shared directory. |
| Project |
Specify the mandatory path to the project tree, starting with $/. |
| User Name |
Specify the mandatory name of the user on Visual SourceSafe server. |
| Password |
Enter the password, that corresponds to the user name.
|
Changes Checking Interval
| Option |
Description |
| Checking interval |
Select a radio button to choose between the global predefined server setting or entering a custom interval for checking VCS for changes.
| Some public servers can block access if polled frequently. |
|
VCS Root Sharing
| Option |
Description |
| VCS Root Sharing |
Enable this option to use this VCS root in other projects or build configurations. See Shared VCS Roots for more information. |
Visual Source Safe