Please be aware that various Source Safe .ini file settings impact the workings of SS.EXE and, therefore, this addin. The following items have been shown to be the most common causes of difficulties reported by users of this addin:SourceSafe Notes
- Be aware that the SourceSafe command line (which is used extensively by the addin) can be configured separately from the Source Safe Explorer interface. Most of the settings in the srcsafe.ini and user's .ini files can be set specifically for the command line interface by appending this string " (CL)" to the setting name. I am not a SourceSafe configuration expert but this has already proved of value in some installations and has been applied to at least the following entries: Force_Dir, Diff_Format, and Data_Path.
- Be sure that the "Force_Dir (CL)" setting in your user's .ini file is set to true. Failure to do so can result in "file not on path" errors. The Source Safe documentation states that this variable is set to true by default but I found a case on my machine where this was not so. In the VSS .ini file for your user id, check to see that BOTH of the following exist:
Force_Dir = Yes
Force_Dir (CL) = Yes
- Note that the Source Safe command line and Explorer interfaces can use different means to locate the Source Safe database. While the Explorer interface can make use of registry settings, it appears that the command line interface uses either the "Data_Path (CL)" setting in the srcsafe.ini file or the SSDIR envirmonment variable value.
- There is a setting in the source safe user's .ini file which can create erroneous diff results (says files are identical when they are not) in the addin. The setting's name is Diff_Format. To net it all out, just don't set it. See the VSS documentation for more details.
- Note that when running the Visual Source Safe Explorer, you can effect the value of .ini file variables via the graphical user interface. In my experience, you must actually exit the program for these changes to be flushed to disk.
- This addin must sometimes parse the console output from the SS.EXE program for tokens that it can recognize. Because VSS is available in internationalized versions, the console output will vary with the language used. The java internationalization mechanisms have been used to support this variation.
At present, resource bundles are provided for English, French, and German versions of VSS. Adding additional support should be an easy matter of creating an appropriate resource bundle for your language and placing it in the .jar file in the /resources directory. Please send me any additions and I will be pleased to incorporate them into future releases.
The addin uses the value for found for SourceSafeLocale in its properties file to search for internationalizes resources. English resources are used as the default if no matching resources are found. Failure to locate a resource bundle which corresponds to your version of VSS will typically result in spurious errors indicating that a file is not on the project path in Source Safe.