© 2000 Microsoft Corporation. All rights reserved.
Other product and company names herein may be the trademarks of their respective owners.
Visual SourceSafe Readme includes updated information for the documentation provided with Microsoftâ Visual Studio® -- Development System for Windows® and the Internet. The information in this document is more up-to-date than the information in the Help system.
Contents - Click any of the items below
Visual SourceSafe version 6.0a is a re-release. It contains a modified installation program and updated VSS files containing all bug fixes made since VSS 6.0 released. This version is intended to upgrade the VSS release included in Microsoft Office Developer version 9.0.
The installation program for VSS 6.0a has been modified to ensure an upgrade of your existing VSS 6.0 installations. Read the Installation section in this document for the latest install directions. For a list of the fixes included in this release, see VSS 6.0a Bug Fixes.
Novell NetWare servers can be configured to handle either long file names or file names in the 8.3 file name format. If the Novell NetWare server can handle only file names in the 8.3 format, the regular Visual Studio installation process cannot install on the Novell NetWare server. To install VSS on a Novell NetWare server that can handle only file names in the 8.3 format, use the following steps.
To install from the Visual Studio CDs:
To install from the Visual SourceSafe standalone compact discs:
Difference for File Dialog Box topic — In the Dialogs section of the Visual SourceSafe documentation, the first paragraph in the Remarks section is incorrect.
Current text: This dialog box is used only when you have not selected the visual difference comparison. (For visual differences, make sure you select the Visual option from the Difference Options dialog box.) By default, VSS uses the Visual Difference dialog box.
Correct text: This dialog box is used only when you have not selected the visual difference comparison. (For visual differences, make sure you select the Visual option from the Difference Options dialog box.) By default, the Visual option is selected, and VSS uses the Differences for <filename> dialog box with options specific to visual differences.
In the File History Options Dialog Box topic of the Visual SourceSafe Documentation, the first sentence of the Labels section is incorrect.
Current text: Includes only labels in project history if you have selected the Include file checkins option.
Correct text: Includes only labels in project history if you have selected the Include file histories option.
In the Advanced Check Out Options Dialog Box topic of the Visual SourceSafe Documentation, the Replace option is incorrect.
Current text: Replace — Replaces the file with a read-only version.
Correct text: Replace — Replaces the file with a writable version.
In the Advanced Check Out Options Dialog Box topic of the Visual SourceSafe Documentation, the End of Line option has been removed.
In the Advanced Get Options Dialog Box topic of the Visual SourceSafe Documentation, the End of Line option has been removed.
VSS 6.x handles MBCS (multibyte character sets) and DBCS (double-byte character sets) differently from earlier versions of VSS. If you are upgrading an existing installation of VSS that has a file called SSUD.dll, rename it so that VSS 6.x does not recognize it. For example, rename the file to SSUD.bak. If you do not rename it, you may have trouble in the IME with font association (FA) turned off or it may generate GPFs when dialog boxes that are new to VSS 6.x are displayed.
VSS 6.0a contains the following bug fixes. References to articles in the Microsoft Knowledge Base are included where appropriate.
When you run the VSS 6.0a Setup program on a computer that has VSS 6.0 with SP1, SP2, or SP3 installed, the Setup program displays the following warning message:
The Installation Wizard has detected a potentially conflicting version of a Visual Studio 6.0 product on your machine. One or both of these products may not work after installing this product. The Readme topic "Side by Side Product Installations" describes the supported combinations.
Do you wish to continue?
This warning is valid because installing VSS 6.0a side by side with VSS 6.0 is not supported. Answer Yes to this message and to a subsequent message asking you if you are certain you want to continue.
When Setup continues, it states that you have an older version of the product already installed and asks whether you would like to upgrade it. Click Next to accept the selected folder location. When prompted for the specific installation type, select the type already installed on your system.
The source code control database maintained by VSS must be on a drive that is accessible to all users working on projects controlled by VSS. The most versatile method of working with VSS is to perform a server installation to a network drive, and a netsetup installation on each workstation.
You will be prompted to replace an existing installation if found. This is recommended, but you can choose an alternate path and then maintain two different databases, one in the old format and one in the new format, on the same computer.
Note Make sure you back up the database before you upgrade.
You will be prompted to convert your database to the new format for faster performance. You should do this only if:
Be aware that a full VSS license is required for each user of Visual SourceSafe. For example, if you have 100 people using your VSS database, you must purchase 100 Visual SourceSafe licenses to avoid violating copyright law.
The version 6.0a Netsetup program requires a CD-Key before it can install the Visual SourceSafe client software to a client computer. To make sure your clients can run Netsetup successfully, give a CD-Key from one of your licensed boxes to each user you recommend Netsetup to. It is acceptable to reuse the same CD-Key for everyone running Netsetup, but you are still required to have an individual license on hand for every user.
Note A full Visual SourceSafe license is required to use Netsetup by each client.
- or -
Visual Studio products with the same version and in the same language—Visual C++ and Visual Basic version 6.0 in English, for example—can be installed separately on the same workstation. Such installations are supported by Microsoft. The Visual Studio 6.0 Installation Wizard detects if other versions of the 6.0 product line have been installed on a workstation.
Mixing different language versions, point releases, or product tiers on the same workstation are generally not supported. This means that the installation can fail, one or more of Visual Studio 6.0 products may not work even if the installation succeeds, or in the worst case you may not be able to remove any of the products completely.
If the wizard generates a warning during installation, the safest course of action is to uninstall the Visual Studio 6.0 product before proceeding. The detection scheme checks for the following scenarios:
|
Product |
Supported Installation |
|
Visual Basic |
Install in two different locations |
|
Visual C++ |
No side-by-side installation is supported. |
|
Visual FoxPro |
Install in two different locations |
|
Visual InterDev |
Install in the same location. You must reinstall after removing one version. |
|
Visual J++ |
Install in the same location. You must reinstall after removing one version. |
|
Visual SourceSafe |
Install in the same location. You must reinstall after removing one version. Note The UI language chosen when you run Visual SourceSafe is based on the system's language settings. If that language is not installed for Visual SourceSafe, it uses English instead. |
|
MSDN |
Install in default directory. |
After an administrator has created a VSS installation on the server, users can run NetSetup to copy the VSS executables to their hard disk.
To install using NetSetup:
Warning to Administrators All users, including anyone running Netsetup, must possess an individual VSS license to install and/or use the product. Netsetup is provided as a convenience, but the administrator should make sure to obtain individual licenses for each person that installs and uses the product.
If you were prompted to upgrade your database to the new 6.x format and you indicated Yes, you now have a 6.x database and can take advantage of label promotion and enjoy performance enhancements. If you weren't prompted or you indicated No to the prompt and you now want to upgrade your database, run the DDUPD.exe command-line utility, which exists in the \win32 directory of your VSS 6.x server installation. (You can either go to that directory and run it or add that directory to your path and run it.) We recommend you run DDUPD only when everyone has quit VSS. The syntax is:
DDUPD <path to data folder> [-undo] [-redo]
To upgrade a 5.0 database, for example, you would run:
DDUPD \\server\share\vss\data
To undo an upgrade, return to the version 5.0 format and stop taking advantage of the performance enhancements and label promotions:
DDUPD \\server\share\vss\data -UNDO
To redo the upgrade process on a database that is already in the new format, run:
DDUPD \\server\share\vss\data -REDO
If you delete a VSS installation (including the database) and then attempt to run Setup, Setup may try to install VSS in the Recycle bin (if the old database is found here). This happens only if the Recycle bin hasn't recently been emptied. To remedy the problem:
Microsoft VSS 6.0 adds many new features. Some of the highlights include:
It is still advisable to back up the drive where your VSS database resides regularly. It is important to use full backups, not incremental or differential backups, to avoid problems.
In addition, you should run the ANALYZE program periodically to maintain database integrity. If a corruption is found, the ANALYZE program can usually repair the problem. Updates to the ANALYZE tool are posted periodically on the VSS Web site, http://www.msdn.microsoft.com/ssafe. You can check that site to see if there is a version of ANALYZE more recent than the one shipped with this product.
To run ANALYZE:
Note It is always advisable to run ANALYZE and back up older databases before upgrading them to the 6.x format.
If you are using VSS on a remote database and you lose your connection to the server, the following error will occur:
"unknown error - 20038," (or similar)
If you see this error, you have lost your network connection.
To correct the situation
VSS uses the date and time that your local computer stores. If your computer is not synchronized with other computers, unpredictable results can occur. For instance, you check in a file after someone else, but VSS thinks your checkin happened first because your system clock was off!
The best solution for this problem is to synchronize your local date and time with the network on a regular basis. With Windows NT this can be done with a Domain Time Source Server. Check the http://www.novell.com/ site for information on time synchronization with Novell NetWare servers.
If you are working from the command line and receive a message stating "No VSS database (SRCSAFE.INI) found. Use the SSDIR environment variable or run netsetup.", set the SSDIR variable. This tells VSS where to find the Srcsafe.ini file for the VSS server installation to which you want to connect. You can do this by typing the following at the Command prompt:
set ssdir=\\server\share\vss
Where \\server\share\vss is the folder where the Srcsafe.ini file is located.
Note There should not be a space between the equal sign and the location of the VSS server installation. For example, the following will not work:
set ssdir= \\server\share\vss.
A shadow folder is a live mirror (on the file system) of the projects in the Visual SourceSafe (VSS) database.
For a shared database, you must set up the shadow folder with a Universal Naming Convention (UNC) path, such as \\Server\Share\Shadow, to avoid failure when changes are made from a computer other than the one used to set up the shadow. Make sure the UNC contains no long names, just eight-character short names for the \\Server\Share\Root portion.
For example, instead of defining the shadow folder as D:\VSSShadow, you can define the shadow folder as: \\server\D\Shadow.
Confirm that all the Visual SourceSafe users have read/write access to the UNC directory.
Due to a problem Windows 95 has accessing some programs on Windows NT Server computers through a UNC that contains long names, you should create a network share on the Windows NT Server computer that points directly to the VSS location on the server's disk drive, and avoid long names for the server and share names as well.
For instance, if VSS is installed to:
D:\Program Files\Microsoft Visual Studio\Common\VSS
You can provide users access to it by setting:
D:\
shared as
\\Long Server Name\Long Share Name
And they would then access it with:
\\Long Server Name\Long Share Name\Program Files\Microsoft Visual Studio\Common\Vss\Netsetup.exe
The long names cause computers running Windows 95 to fail when the server is a computer running Windows NT.
Instead, set it up with:
D:\Program Files\Microsoft Visual Studio\Common\VSS
shared as
\\Server\VSSShare
In this way, users can access Netsetup.exe with the following short UNC:
\\Server\VSSShare\Netsetup.exe
Microsoft VSS has a home page on the Internet. This home page features a variety of information including articles on VSS, a self-running demo that you can download, a collection of helpful VSS utilities, and much more. The URL for the home page is: http://www.msdn.microsoft.com/ssafe.
If you encounter problems or have questions not addressed here or in the online documentation, you can search the Microsoft Knowledge Base at http://support.microsoft.com/support. The Knowledge Base is also available on the MSDN Library Visual Studio 6.0, included on the CD-ROM with Visual SourceSafe.
You can exchange information with other VSS users by visiting the microsoft.public.visual.sourcesafe newsgroup on the Internet. This newsgroup is on the msnews.microsoft.com server.
Note Microsoft does not provide support for messages posted to the newsgroup.