Using VSS in Net to implement Version Control Management

URL: http://www.cnblogs.com/skylaugh/archive/2006/08/17/479750.html

Initial warehouse receiving
Method 1:
Step 1: Use.. NET connects to the source VSS database to be imported into the VSS controlled center database, and creates a local path to store the solution in the source VSS library. If the project is a WEB project, you will also need to create a local path corresponding to the WEB virtual path, which is used to store the WEB project file. After the above two directories are created, they will be in. NET to see the solution in the opened source VSS library. Compile the program for the first time and check whether the solution in the obtained VSS source library is correct. If the compilation is successful, go to our second step;
Step 2: In. under the "file" menu of. NET, choose "Source code management"> "Change source code management", and click "Unbind" in the displayed dialog box ", the purpose of this operation is to disassociate the solution from the VSS server and convert it into a pure local file. Then, the second compilation is performed, the compilation is passed, and VS is disabled.. NET. Open the resource manager and go to step 3;
Step 3: Find the two directories created in step 1 in the resource manager. At this time, all the project files and WEB project files under the source VSS library are under the directory, in this case, we need to delete some files related to the source VSS database, search for files, find the files of VSS and SCC in these two directories, and delete all of them, then go to step 4;
Step 4: Open.. NET, open the solution file under the directory we created, and then we will see that this solution runs in a separate relationship with any VSS library, and runs our third compilation, if the solution is compiled, right-click the solution and select "add solution to source code management" in the pop-up menu. The "add solution to source code management" dialog box appears, and enter the project name, click "OK". Now we have to wait quietly for.. NET adds the project and project files we obtained from the source VSS library to our own VSS controlled center library. After adding the files, go to Step 5;
Step 5: Disable.. NET solution. Under the "file" menu, choose "Source code management"> "open from source code management" to connect to our VSS controlled center, open the newly added project solution. If you are prompted that the reference file cannot be found, right-click the project in Solution Explorer, in the Properties dialog box of the project, add the reference path of the project and perform the fourth compilation. If the compilation is successful, package the project file through the copy project under the "project" menu, this package can be used as an executable package for testing by testers and then enters Step 6;
Step 6: Check in the solution and project files at this time, close the solution after you check in, and close. NET, then open VSS Explorer, right-click the project we checked in VSS Explorer, and select the "Label" menu. Enter the project version information and comments, and click "OK ", the initialization of the VSS controlled central database is completed, and maintenance and upgrade will be performed later.
Method 2:
NOTE: With the introduction of the previous method, there should be a basic process and basic idea of using VSS for version control. In accordance with the same principle of the previous method, you can also follow these steps.
Step 1: Open VSS Explorer, connect to the source VSS library, right-click the project root directory in the left-side window of VSS Explorer, and select "Get Latest Version ...", Obtain the project file and put it in a specified directory. Close VSS Explorer and go to step 2;
Step 2: Open the resource manager, find the file directory specified in step 1, find all VSS and SCC files in the directory, delete these files, and go to step 3;
Step 3: Open VSS Explorer, connect to the self-created VSS controlled center library, and create a project under this library. The project name is determined by the actual development project and naming rules, after the project is created, go to step 4;
Step 4: select the project you just created and click "Add Files…" under the "File" menu ...", Add all the project files modified in step 2 under the directory specified in step 1 to the VSS Explorer project. After adding the files, go to Step 5;
Step 5: Open.. NET, connect to the VSS controlled central database, and open the solution in the project we just created. At this time, we need to create VS in the same way as the method.. NET solution and WEB project file directory. After loading the solution in the VSS controlled center library, go to Step 6;
Step 6: run the first compilation. If the compilation passes. under the "project" menu of. NET, click "Copy project" to package the solution. This package is distributed to testers for testing and then enters Step 7;
Step 7: In.. NET to check out the VSS library solution and all project files. If the files are compiled successfully, check in the VSS controlled center library. After the files are checked in, close. NET, then open the VSS Explorer, right-click the project we created, select "Label", set the project version information and comments, and the initial warehouse receiving step of this method is completed.
Subsequent version warehouse receiving:
Method 1:
Step 1: Open. NET, connect to our VSS controlled center library, open the project solution specified in the VSS controlled center library, after opening, check out all files in the solution to the project file directory and the specified WEB project directory created when opening, and go to step 2;
Step 2: Start another. NET, from the "file" menu-> "Source code management"-> "open from source code management", connect to the VSS source library of subsequent versions, and open the solution in the VSS source library of subsequent versions, after opening the file, check out all files in the solution of the subsequent version to the project file directory and the specified directory of the WEB project, make sure that the directory created in this step is not the same as the directory created in step 1, and then go to step 3;
Step 3: Copy all project files under the directory created in step 2 to the directory created in step 1, and replace all project files under the directory created in step 1, step 4;
Step 4: Check In.. NET, including the reference path of the project file. Run the compilation. If the compilation is successful, check the solution to our VSS controlled center library, close. NET to enter Step 5;
Step 5: Open VSS Explorer, right-click the project, select "Label", reset the version information and comments of the project, and click "OK". The subsequent versions are successfully added.
Method 2:
Step 1: Use VSS Explorer to connect to the controlled center. CheckOut should add the last version of the new version of the VSS controlled database to a specified working directory and go to step 2;
Step 2: Use VSS Explorer to connect to the new version of VSS source library, get all its project files to a specified directory, and then go to step 3;
Step 3: Copy all project files in the directory specified in step 2 to the directory specified in step 1 and overwrite all directories and files with the same name to go to step 4;
Step 4: Open VSS Explorer and connect to the controlled center. In the first step of CheckIn, specify all the files in the directory and go to Step 5;
Step 5: Open.. NET, connect to the VSS controlled central database at this time, and open the project solution. If an error message is prompted when you open the project solution, modify it accordingly and run the compilation, if the compilation is successful, go to Step 6;
Step 6: Open VSS Explorer again, right-click the project, select "Label", and set a new version and comment information for the project. So far, use method 2 (Make full use of VSS Explorer) the initial warehouse receiving and subsequent warehouse receiving operations are completed.

URL: http://www.cnblogs.com/skylaugh/archive/2006/08/17/479750.html

Initial warehouse receiving
Method 1:
Step 1: Use.. NET connects to the source VSS database to be imported into the VSS controlled center database, and creates a local path to store the solution in the source VSS library. If the project is a WEB project, you will also need to create a local path corresponding to the WEB virtual path, which is used to store the WEB project file. After the above two directories are created, they will be in. NET to see the solution in the opened source VSS library. Compile the program for the first time and check whether the solution in the obtained VSS source library is correct. If the compilation is successful, go to our second step;
Step 2: In. under the "file" menu of. NET, choose "Source code management"> "Change source code management", and click "Unbind" in the displayed dialog box ", the purpose of this operation is to disassociate the solution from the VSS server and convert it into a pure local file. Then, the second compilation is performed, the compilation is passed, and VS is disabled.. NET. Open the resource manager and go to step 3;
Step 3: Find the two directories created in step 1 in the resource manager. At this time, all the project files and WEB project files under the source VSS library are under the directory, in this case, we need to delete some files related to the source VSS database, search for files, find the files of VSS and SCC in these two directories, and delete all of them, then go to step 4;
Step 4: Open.. NET, open the solution file under the directory we created, and then we will see that this solution runs in a separate relationship with any VSS library, and runs our third compilation, if the solution is compiled, right-click the solution and select "add solution to source code management" in the pop-up menu. The "add solution to source code management" dialog box appears, and enter the project name, click "OK". Now we have to wait quietly for.. NET adds the project and project files we obtained from the source VSS library to our own VSS controlled center library. After adding the files, go to Step 5;
Step 5: Disable.. NET solution. Under the "file" menu, choose "Source code management"> "open from source code management" to connect to our VSS controlled center, open the newly added project solution. If you are prompted that the reference file cannot be found, right-click the project in Solution Explorer, in the Properties dialog box of the project, add the reference path of the project and perform the fourth compilation. If the compilation is successful, package the project file through the copy project under the "project" menu, this package can be used as an executable package for testing by testers and then enters Step 6;
Step 6: Check in the solution and project files at this time, close the solution after you check in, and close. NET, then open VSS Explorer, right-click the project we checked in VSS Explorer, and select the "Label" menu. Enter the project version information and comments, and click "OK ", the initialization of the VSS controlled central database is completed, and maintenance and upgrade will be performed later.
Method 2:
NOTE: With the introduction of the previous method, there should be a basic process and basic idea of using VSS for version control. In accordance with the same principle of the previous method, you can also follow these steps.
Step 1: Open VSS Explorer, connect to the source VSS library, right-click the project root directory in the left-side window of VSS Explorer, and select "Get Latest Version ...", Obtain the project file and put it in a specified directory. Close VSS Explorer and go to step 2;
Step 2: Open the resource manager, find the file directory specified in step 1, find all VSS and SCC files in the directory, delete these files, and go to step 3;
Step 3: Open VSS Explorer, connect to the self-created VSS controlled center library, and create a project under this library. The project name is determined by the actual development project and naming rules, after the project is created, go to step 4;
Step 4: select the project you just created and click "Add Files…" under the "File" menu ...", Add all the project files modified in step 2 under the directory specified in step 1 to the VSS Explorer project. After adding the files, go to Step 5;
Step 5: Open.. NET, connect to the VSS controlled central database, and open the solution in the project we just created. At this time, we need to create VS in the same way as the method.. NET solution and WEB project file directory. After loading the solution in the VSS controlled center library, go to Step 6;
Step 6: run the first compilation. If the compilation passes. under the "project" menu of. NET, click "Copy project" to package the solution. This package is distributed to testers for testing and then enters Step 7;
Step 7: In.. NET to check out the VSS library solution and all project files. If the files are compiled successfully, check in the VSS controlled center library. After the files are checked in, close. NET, then open the VSS Explorer, right-click the project we created, select "Label", set the project version information and comments, and the initial warehouse receiving step of this method is completed.
Subsequent version warehouse receiving:
Method 1:
Step 1: Open. NET, connect to our VSS controlled center library, open the project solution specified in the VSS controlled center library, after opening, check out all files in the solution to the project file directory and the specified WEB project directory created when opening, and go to step 2;
Step 2: Start another. NET, from the "file" menu-> "Source code management"-> "open from source code management", connect to the VSS source library of subsequent versions, and open the solution in the VSS source library of subsequent versions, after opening the file, check out all files in the solution of the subsequent version to the project file directory and the specified directory of the WEB project, make sure that the directory created in this step is not the same as the directory created in step 1, and then go to step 3;
Step 3: Copy all project files under the directory created in step 2 to the directory created in step 1, and replace all project files under the directory created in step 1, step 4;
Step 4: Check In.. NET, including the reference path of the project file. Run the compilation. If the compilation is successful, check the solution to our VSS controlled center library, close. NET to enter Step 5;
Step 5: Open VSS Explorer, right-click the project, select "Label", reset the version information and comments of the project, and click "OK". The subsequent versions are successfully added.
Method 2:
Step 1: Use VSS Explorer to connect to the controlled center. CheckOut should add the last version of the new version of the VSS controlled database to a specified working directory and go to step 2;
Step 2: Use VSS Explorer to connect to the new version of VSS source library, get all its project files to a specified directory, and then go to step 3;
Step 3: Copy all project files in the directory specified in step 2 to the directory specified in step 1 and overwrite all directories and files with the same name to go to step 4;
Step 4: Open VSS Explorer and connect to the controlled center. In the first step of CheckIn, specify all the files in the directory and go to Step 5;
Step 5: Open.. NET, connect to the VSS controlled central database at this time, and open the project solution. If an error message is prompted when you open the project solution, modify it accordingly and run the compilation, if the compilation is successful, go to Step 6;
Step 6: Open VSS Explorer again, right-click the project, select "Label", and set a new version and comment information for the project. So far, use method 2 (Make full use of VSS Explorer) the initial warehouse receiving and subsequent warehouse receiving operations are completed.