VSS project Branch

VSS project Branch
Classification: VSS source code management ()
Suppose there is a solution demo1/Project demo1 ($/demo/demo1/demo1) in the demo root directory, and another layout book &/demo/demo2/demo is required.

First, create the solution directory demo2 (&/demo/demo2/demo2) under the demo directory, right-click the demo2 pop-up shortcut menu, and select "share to &/demo/demo2... "menu item.

The share to &/demo/demo2 dialog box is displayed. Select the &/demo/demo1/demo1 project directory. Select the check box "branch after share" (indicating that the project branch is an independent branch; otherwise, it is a shared Branch), and then click "share.

The share &/demo/demo1/demo1 dialog box is displayed. In the "new name" text box, enter the new project directory name, select the check box "recursive" (all subfolders under the project directory will be created), and click "OK" to complete the project branch.

VSS branch function: the new branch created in 31vss will appear in the form of a new project

For example, for a Development Group that is developing ABC system 1.0, they can use the VSS branch function as follows:

1. "$/ABC system" is the backbone, and the development team will perform the latest development on this project;

2. When 1.0 is complete, the development team • Right-click the "$" node in VSS and select "share ..." • In the displayed dialog box, select the "$/ABC system" project, select "branch after share" in the lower right corner, and click "share". • In the subsequent dialog box, name the new project "ABC system 1.0 branch"

3. A new project "$/ABC system 1.0 branch" appears ". This is a branch of the trunk "$/ABC system.

4. the development team can use functions such as check out/check in on the branch as usual. If you need to merge the changed files on the branch back to the trunk, right-click the merged file and select "merge branches…" from the "sourcesafe" menu ..." You can. VSS is still very strong