Visual SourceSAFT6.0 User Guide LeafinWind
1 Introduction to Visual SourceSafe Visual SourceSafe is a Microsoft's document version management tool, which has been developed by Visual Studio6.0 and Visual Studio.net. His features are mainly easy to use, high visualization, and through network sharing to implement document sharing in the LAN, compare version management of document code developed by small team development. 2 Program Group Profile Visual SourceSaft provides users with four management tools, as shown below: where: Visual SourceSafe6.0 Admin Program is mainly for project CVS administrators, mainly operated users management, VSS database management, engineering permission Management, database backup management, and some default settings in the database. ^ _ ^, Let you find the feeling of the network management, who wants to play who is playing, but remember "the bigger the power, the greater the responsibility." The Microsoft Visual SourceSafe 6.0 program is primarily for programmers, checkin, check out, check out, file version management, which is also the most commonly used program, which is also very weak, of course It is a tool that is mentally useful, this is the characteristics of MS. Other two mainly after some abnormal conditions (such as Checkin files, server crash) work for some database errors and fixes. If Analyze VSS DB is used to analyze the quality of the database, the Analyze & Fix VSS DB adds the function of the database repair on the former. I have never used it once, I don't say much. 3 Some basic concepts of document version 3.1 File server version (controlled version) and file local version (uncontrolled version): When you use a similar document version control software, you must first clarify these two Concept. Many people who have just started using the document version of the software often do not have these concepts. At particular, some single-machine version control software often controls the version management software directly controls the local file, records its modification process and file versions. . In fact, it is not, when using the version control software, we must clarify the two versions of the document, which is the single-machine version of the software to separate theory. One is the server version of the file. This version is definitely a version of the version management software protection and management, and the user can only affect and change this version through the limited operation of the management software authorization. At the same time, it is also necessary to emphasize that this version is also a shared version, and users with system-authorized users can access. One is the local version of the file, which is a version that is not controlled by the version management software. We cannot directly modify the server version of the file, but you can modify the local file directly. Haha! For local files, you have everything. However, it is necessary to emphasize the concept of establishing a server's documentation. 3.2 Basic Workflow and Principle of Version Control Software 1. First, User A Gets one of the latest versions of file f on the server, such as version 8, download (Download) to local, form a local version of the file. 2. Then modify the file locally. After the local file is modified, the user A changes to the service (UPLOAD) file and updates the version of the file F to 9. 4. Next, user B also started to download the latest version of File F. At this time he gets a version is 9. Thus, the file obtained by the user B includes the modification of User A. 5. The above process is then repeated, and the version 10 of the file F is formed on the server.
This version 10 contains modifications of user A and user B. We can see the basic process used by version control software, which is also a mechanism for keeping and spreading each user's modification. The process is shown below: By the above we can see that the basic working principle of the file version control software is that each user gets a version of the file from the server, and based on this version to make changes, the modification is completed to the server. Her own modification. The server controls the control and fusion of each user through its own version management mechanism, and forms a new version of the file and shares it. 3.3 File lock The process of the above mentioned mentioned flow, if the user b is downloaded by User A, the file F file version is downloaded. It is clear that it downloads version 8, there is no user a modification. If the user B is submitted to modify the modification formation 10, the modification of the user A is stored in version 9, and the latest version 10 has lost the modification of the user A in the version 10. It will cause the user to modify the loss of data. The reason why this to modify the data loss is that multiple users make changes to the same version of the file, which is submitted, and the latest file versions are lost in the latest file versions. As shown in the figure below: So how to avoid this situation, some of the powerful version control software uses complex version conflict detection and fusion technology. Some simple management software adopts file lock technology. Simply put, the file lock technology allows a version of the user who modifies the server-side file. This is what is achieved, and in the Visual SourceSafe is a check-in and checkout (Checkout). Checkout is to lock the file on the server side. Checkin is submitted to modify and unlock the file. When a user is going to modify a file, the process is as follows: 1. User A checks out file f and locks the file, download the latest version 8 2. User A Document 8 3. User A completes the modification, submits the modification to the server, forms the latest version 9 of the file f, and unlocks the server's file f. 4. File f is unlocked to have user B to check out, this is user B Download version of the version containing User A. 9 5. Repeat the appeal process. Since a file can only be locked once, it is obvious that all Checkout operations of user B have failed before the user A checks out this file, check in (checkin). This ensures that the above process is also guaranteed to modify the user A and the user B and modify the integrity of the data. 3.4 Server Directory and Work Contents There is a figure above. It can be seen that the user client of the VSS system operates two places, one is the file on the server, one is local storage to modify the directory of editing files. Generally, the file version management system does not directly exposes the physical path stored by the server-side file directly, and only gives a virtual logic path, in the VSS, the roots of the virtual path without the database are "$ /" , Then there is no project directory to hook the root below the tree structure. We call the virtual directory of the project called the server directory. The physical directory of the temporary modification file locally is called a work directory. Obviously, we have to correspond to the virtual directory of each item and the local working directory, so that the file can be interactive between the server and the local.
3.5 VSS The most common version of the Get Latest version: Synchronize operation, just get the latest version of the file CHECK OUT: plus file lock, by default, will include Get Latest version operation. Check in: Solve the file lock, Local modification. Ok, there are some basic concepts of some basic file versions management, and there will be no more confusion when you talk about some basic operations.
