Microsoft Corporation
June 1998
You can use Microsoft® Visual SourceSafe™ (VSS) with your Microsoft Visual InterDev™ project to keep track of changes to your files. To install Visual SourceSafe and set it up to work with Visual InterDev, you need to complete several procedures using a couple of different interfaces.
The following table outlines the main tasks needed to set up source control with Visual InterDev. The steps for each of these tasks are detailed in the sections under "For more information," which appear later in this paper.
Table 1. Steps to set up source control in Visual InterDev
Main task | For more information |
Use Visual SourceSafe Setup to install Visual SourceSafe on the server | Installing Visual SourceSafe |
In Visual SourceSafe, grant Visual SourceSafe permission to users | To grant permissions to a user |
For Web servers on Windows NT®, add permissions to the anonymous user account | To add permissions for the anonymous user account |
In Visual InterDev, add a Web project to source control | To enable source control for Web pages |
To solve or avoid problems | Troubleshooting Source Control |
When installing Visual SourceSafe, be sure to install the Visual SourceSafe server on the same computer as the Web server and make sure the option for integration with other visual products is selected. Without that option set, Visual SourceSafe runs independently and does not recognize the commands used by Visual InterDev.
The following procedure assumes you have Microsoft® Internet Information Server (IIS) and FrontPage® Server Extensions already installed on your Web server.
Note If the server machine is a Windows 95 computer, make sure that someone remains logged into Windows 95. Often users of the server end their work by using the shutdown option "Close all programs and log on as another user." This option leaves the server at the login prompt and the integration between Visual SourceSafe and Visual InterDev does not work when there is no one logged onto the server.
If you want the Visual SourceSafe database to reside on a different server than your Web server, you need to specify additional settings. The following procedure assumes you already have your Web server installed.
Note Be sure to give the anonymous account the same password as on the Internet Information Server machine and make sure it has log on locally permissions. If you ever change the password on one machine, you need to change the password for both machines to keep them the same.
You need to make sure the passwords and permissions for the anonymous accounts on both machines are the same, otherwise attempts to use source control will generate errors. For more information about common errors, see "Related Error Messages" in the section "Troubleshooting Source Control."
Visual SourceSafe provides two ways to control source files.
If you want to enable multiple check outs, you need administrator privileges to the Visual SourceSafe Administrator on your server.
Any of the files can be checked out and worked on simultaneously. After one person has checked the file back in, others can merge their changes using the Visual SourceSafe merge options available when they check in the file.
After you've installed Visual SourceSafe on a Web server, you must grant read/write permissions to all users whom you want to be able to author files using Visual InterDev or FrontPage.
Note If you assign a password, the user has an additional login step to complete when using the project.
In addition to granting read/write permissions to specific users, if you have installed Visual SourceSafe on a Windows NT server, you must also add permissions for the anonymous user account.
Note By default, this property setting is IUSR_machinename, where machinename is the name of the server where you have installed the Visual SourceSafe Administrator.
When Visual SourceSafe tracks changes, it uses the operating system to identify and record who made the changes.
Certain operating systems can only recognize and record the anonymous user name for changes. If your Web server is running Windows 95, or Windows NT using the File Allocation Tables (FAT) file system, then all files checked out through Visual SourceSafe will always be checked out to the same user account. This user account might not represent the user performing the operation.
On a Windows NT FAT system, the anonymous user account performs all source control operations on the server. On a Windows 95 system, the user account specified when Windows 95 was started performs all source control operations on the server.
Once you've installed and set up Visual SourceSafe, you can enable source control for your Web pages using any Web project that references those pages. Only one developer needs to enable source control for the application.
Note It's recommended that you use a different name than that of the Visual InterDev project such as $/MyWebApplication_Web. The name must be preceded by the dollar sign ($) and forward slash (/).
If you do not know whether Web pages have source control enabled, you can check the property sheet for your project that references those Web pages.
You can also disable source control for Web pages from any Web project that references those Web pages.
When you disable source control for Web pages, the Visual SourceSafe project created when you first enabled source control for those Web pages remains on the Visual SourceSafe server. This means you can reenable source control and choose that Visual SourceSafe project for your Web pages. This may cause some unexpected results, however.
For example, if you disable source control, then delete files from the Web project, then reenable source control, the files that you deleted will show up in your Web project again. This happens because the files were deleted outside of source control and so the original Visual SourceSafe project still shows them as part of the project. You can remove the Visual SourceSafe project by deleting it from within Visual SourceSafe Explorer.
If you experience difficulty in using Visual InterDev with Visual SourceSafe, you may need to make changes outside of Visual InterDev in the applications that support Visual InterDev. You can check the following items to resolve issues with enabling and using Visual InterDev with Visual SourceSafe.
You do not need Visual SourceSafe on your local computer; you only need Visual InterDev. If you want to use the Visual SourceSafe Explorer to work with your Web files directly in the VSS database, you can install the Visual SourceSafe client on your local computer.
For more information about installing and setting up a Visual SourceSafe database, see "How to Install VSS" in the Visual SourceSafe documentation.
If Visual InterDev doesn't recognize that Visual SourceSafe is installed on the server, try these tips.
The Windows NT Event Viewer on the IIS server often contains information that can help locate the cause of a problem if integration is not working. These log errors usually come in pairs, the topmost of which usually contains an error number and the one below it a short description of the error.
Although errors might differ depending on how the components are configured, the table below shows commonly encountered errors and possible solutions.
Table 2. Error messages and solutions
Message | Solution |
Source Control System Failure: File "srcsafe.ini" not found |
Reinstall Visual SourceSafe, select Custom and select the Visual Studio integration option. |
Source Control System Failure User <username> not found |
Add the user to the Visual SourceSafe database. |
Source Control System Failure Could not find VSS resource DLL |
Set the permissions for the anonymous or user accounts to have the correct NTFS file permissions. |
Source Control System Failure Access to file "<path>\srcsafe.ini" denied |
If the Web server and the Visual SourceSafe database are on separate machines, disable NTLM. |
Source Control System Failure Access to file "<path> \um.dat " denied |
If the Web server and the Visual SourceSafe database are on separate machines, disable NTLM. |
Source Control System Failure Invalid handle |
If the Web server and the Visual SourceSafe database are on separate machines:
(a) Change the password for the anonymous account so that it is the same on both machines. - or - (b) Give the anonymous account permission to log on locally to the Visual SourceSafe machine. |
Error: The server was unable to logon the Windows NT account <anonymous user account> due to the following error: Unknown user name or bad password. | Go to the Internet Information Server machine
(a) Enable the anonymous user account in User Manager. - or - (b) Give the anonymous account Log on locally permissions - or - (c) Change the password for the anonymous account in Internet Information Server and User Manager to match. |
If you want more information about Visual SourceSafe, visit the Visual SourceSafe site at http://msdn.microsoft.com/ssafe/.