Using Siebel Tools > Customizing Your Tools Environment > Process for Integrating With Third-Party Source Control >
Example of Integrating with Microsoft Visual SourceSafe
The following sections provide you with examples for using Microsoft Visual SourceSafe.
Check In Example
You have two projects checked out that you want to simultaneously check in to the server and to the source control software. The projects selected are "Project A" and "Project B." The latest version of Project A.sif in Visual SourceSafe is 6, and the latest version of Project B.sif is 5.
When you click the Check In button, the following sequence occurs:
- Project A and Project B are checked in to the server repository.
- C:\Siebel\7.7\tools\bin\srcctrl.bat is invoked. This carries out steps 3, 4, and 5.
- Project A.sif and Project B.sif are checked out and locked in Visual SourceSafe.
- Project A is exported to
tools\temp\projects\Project A.sif, and Project B is exported to
- Project A.sif and Project B.sif are checked in to Visual SourceSafe. The version numbers are incremented so that the latest version of Project A.sif in Visual SourceSafe is version 7, while Project B.sif is version 6.
Revert to Previous Version Example
Consider the situation in which an erroneous definition of Project A has been checked in to the server repository. This is stored in Microsoft Visual Source Safe as version 5 of Project A.sif. You want to revert to version 4 of Project A, since that does not contain the errors.
- Check out version 4 of Project A.sif from Visual SourceSafe into C:\sea7xx\tools \temp.
- Check out Project A from the server repository.
- Import Project A.sif into the local repository using the Overwrite option to resolve object definition conflicts. This replaces the existing definition of Project A with the one in the archive file.
- Check Project A in to the server repository. Project A.sif is automatically checked in to Visual SourceSafe as version 6.