INFO: Branching or Separating SourceSafe Files and Projects

Last reviewed: May 23, 1997
Article ID: Q132921
The information in this article applies to:
  • Microsoft SourceSafe for Windows, version 3.1
  • Microsoft SourceSafe for MS-DOS, version 3.1
  • Microsoft SourceSafe for Windows NT, version 3.1

SUMMARY

Creating a branch is useful when you want to continue along two different directions in a single application.

MORE INFORMATION

After sharing the file, you can choose to separate immediately (branch) by selecting the 'Separate after share' checkbox. The steps for doing this are listed below. The other option, is to separate after you have previously shared the file. In the interface, selecting the Separate option on the SourceSafe menu item does this. You cannot, however, create a branch of a project in a subproject of that project. The error "A project cannot be shared under a descendant" will occur.

Because branching is an extension of share, you can also branch files and projects at a specific version.

More information on sharing can be found in the following articles:

      ARTICLE-ID: Q132922
      TITLE     : Sharing SourceSafe Files

      ARTICLE-ID: Q132923
      TITLE     : Sharing SourceSafe Projects

Step-by-Step Example

  1. Highlight the project that you want to share.

  2. Select SourceSafe from the menu, then select Share.

  3. Choose the project.

  4. Select the Separate after share checkbox.

  5. Select the Share push button.

  6. Select the Recursive checkbox.

  7. Select the OK push button.

Notice that the new project's files do not have the multiple pages icon. If you make changes to these files, they will not be reflected on the original project.


Keywords : kbusage SourceSafe ss3 vbwin kbusage
Version : 3.10
Platform : MS-DOS NT WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.