Using Siebel Tools > Customizing Your Siebel 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 "ProjectA" and "ProjectB." The latest version of ProjectA.sif in Visual SourceSafe is 6, and the latest version of ProjectB.sif is 5.
When you click the Check In button, the following sequence occurs:
- ProjectA and ProjectB are checked in to the server repository.
- SIEBEL_TOOLS_ROOT\BIN\srcctrl.bat is invoked. This carries out steps 3, 4, and 5.
- ProjectA.sif and ProjectB.sif are checked out and locked in Visual SourceSafe.
- ProjectA is exported to SIEBEL_TOOLS_ROOT\TEMP\projects\ProjectA.sif, and ProjectB is exported to SIEBEL_TOOLS_ROOT\TEMP\projects\ProjectB.sif.
- ProjectA.sif and ProjectB.sif are checked in to Visual SourceSafe. The version numbers are increased so that the latest version of ProjectA.sif in Visual SourceSafe is version 7, while ProjectB.sif is version 6.
Revert to Previous Version Example
Consider the situation in which an erroneous definition of ProjectA has been checked in to the server repository. This is stored in Microsoft Visual Source Safe as version 5 of ProjectA.sif. You want to revert to version 4 of ProjectA, because it does not contain the errors:
- Check out version 4 of ProjectA.sif from Visual SourceSafe into SIEBEL_TOOLS_ROOT\TEMP.
- Check out ProjectA from the server repository.
- Import ProjectA.sif into the local repository using the Overwrite option to resolve object definition conflicts. This replaces the existing definition of ProjectA with the archived version.
- Check ProjectA in to the server repository. ProjectA.sif is automatically checked in to Visual SourceSafe as version 6.