Problems when using Visual SourceSafe
Visual SourceSafe does not support triggers
Most Version Control systems support some ability to execute programs or scripts when certain events are ‘triggered’ in the Version Control System.
Visual SourceSafe does not support this concept, and so the UD6/CMtool Driver cannot use the INUSE file to determine the location of ‘checked out’ files.
March Hare supply an alternative technique for when Visual SourceSafe to locate the ‘checked out’ files, using additional parameters in the assignment file, SHADOW-FOLDER and SANDPIT. E.g.:
USYS$UD6_PARAMS=shadow-folder v:\, sandpit c:\sandpit
How to use the driver with Visual SourceSafe (cont.)
Configuration information
Taking control in Visual SourceSafe
Releasing a form using Visual SourceSafe
Checking a form in using Visual SourceSafe
Adding a form using Visual SourceSafe
Finding the differences in versions using Visual SourceSafe
Problems when using Visual SourceSafe
UD6 Overview
A methodology to Uniface source code control
Using UD6/CMtool and Uniface with Visual SourceSafe.
$Revision: 1.11 $ $Date: 2011/02/28 02:56:33 $ | [go to top] |