Home      FAQ      Idea Exchange      Ask a Question      My Stuff      Help   
  
Client setup for Microsoft VSS integration
Question
ID
68
Category
Integration (PRO)
  Source Control
Date Created
3/18/2003 4:39:11 AM
Date Updated
12/15/2009 9:40:30 AM
How to setup client for Microsoft VSS integration?
Answer
For each record with associated check-ins BUGtrack generates group of links on the record view page in a form of URLs with custom protocol (vss://) which can be used to visualize changes.
Please note that the user must have SourceSafe client installed (to use its automation objects) and his/her machine must be able to reach the VSS database.

For VSS 2005 save vssviewer.wsf - 'vss://' protocol handler locally and register it (run vssviewer.wsf /register).

For VSS 6.0 save VSSViewer.exe - 'vss://' protocol handler locally and register it (run VSSViewer.exe /register).
VSSViewer.exe uses DiffMergeCTL.ocx file to visualize differences, but some minimal installations of Visual Studio do not include it. If DiffMergeCTL.ocx is already on your system, you shouldn't have any problem.
If you get nothing or an error when trying to see differences, follow these instructions:
Download the DiffMergeCtl.ocx file and place it in the same folder as the file ssus.dll (usually …\VSS\WIN32). Register the file DiffMergeCTL.ocx using RegSvr32.exe

For server setup see Configuring Microsoft VSS server for integration.
Was this information helpful?
 
Back to Search Results