Setting Up Visual Source Safe Integration

Visual SourceSafe doesn't support running triggers for every check-in. Fortunately, there's a trick you can use to get information about check-ins to Vault anyhow. You can tell Visual SourceSafe to keep a journal file, and then use a scheduled task to extract information from this file. Here's how to set this up:

1. Run the Visual SourceSafe 6.0 Admin program. Select Options from the Tools menu. On the General tab, enter the name of a file that Visual SourceSafe should use as a journal file. Click OK to save your change, and close the Admin program.

2. Install Visual SourceSafe to the FogBugz server machine. You must make sure that the FogBugz user or whoever you installed FogBugz to run as has read access on all your VSS folders and all subfolders. The user must also have full control on the names.dat and the rights.dat files, and the LoggedIn directory. Also, the user must have full control on the files SSUS.DLL and SSAPI.DLL in order to create the SourceSafe COM object.

3. Edit the vss_fbupdate.wsf file in the FogBugz\Accessories\SourceControl\VSS folder:

• Edit the FB_PATH variable so that the script will pick up the needed info from the registry. (Note that you will have to add VSSUser and VSSPassword keys to the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Fog Creek Software\FogBugz\[%FB_PATH%].)

• Alternatively, you can override what is in the registry and manually set the sDBConnection to the connection string for FogBugz, and the FB_VSS_USER and FB_VSS_PASSWORD variables.

• For each VSS project you have, add a line to the script beneath the commented-out line

'Call ProcessVSSJournal("Project Name", "Path to VSS Database directory") For example (enter this as a single line in the file): Call ProcessVSSJournal("Test", "

C:\program files\microsoft visual studio\common\vss")

0 0

Post a comment