Visual SourceSafe Configuration
Complete the following procedure for each
Integration Server user that will use Visual SourceSafe (that is, for whom you will create a mapping, as described in
Configuring Access to the VCS
Repository).
To configure Visual SourceSafe for an
Integration Server user
1. Identify the Visual SourceSafe database to the user's Windows system, as follows:
a. Right click My Computer and then click Properties.
b. Click the Advanced tab and then click Environment Variables.
c. In the System variables table, do the following:
a. To the Path variable, add the fully qualified path to the Visual SourceSafe folder that contains the binary files for commands and the ssexp.exe file.
b. Add the variable SSDIR and set it to the fully qualified path to the Visual SourceSafe database.
d. Click OK three times.
Note:
These instructions are for Windows XP Professional. Instructions for other Windows systems might vary slightly.
2. Set Visual SourceSafe client options as follows:
a. Start the Visual SourceSafe client.
b. Click Tools, then click Options.
c. Click the Local Files tab, clear the Append end-of-line to all text files check box, and click OK.
d. It is recommended that you configure Visual SourceSafe to check in unchanged files. Doing so ensures that check in comments are recorded for all elements, and that all related files that have been checked out with a package, folder, or element will have their VCS version numbers incremented simultaneously. Click the General tab, select Check in from the Check in unchanged files list, and click OK.
e. If Visual SourceSafe is configured to use a text editor such as Notepad for viewing files, the text editor will open each time the VCS Integration feature checks in a file to the Visual SourceSafe repository. To avoid this, remove the text editor specification. Click the General tab, delete the text in the Editor for viewing files box, and click OK.