Version Control Software Microsoft Visual Souce Safe6.0
Microsoft Visual Souce Safe6.0 is the version control software developed by Microsoft. It is used in the process and version management of software development. It has convenient management and simple characteristics, which is very suitable for team development process and version control. The use steps are described as follows:
1. installation
In the process of using Microsoft Visual Souce Safe6.0, it is usually used as a server as a server, used to unify the software, centralized storage management; other client machines Connect the corresponding database on the server to implement client machines The version is consistent (or using a client machine as a server, here: Server and client machines are only conceptual calls to use higher performance machines as server machines).
(1) server side installation
Install "Visual Source Safe 6.0" software in Microsoft Visual Studio 6.0, install it under the specified path, usually "C: / Program Files / Microsoft Visual Studio" (users can make appropriate modifications according to their own situation) The "Visual Source Safe 6.0" server software is located in the "CommON / Vss" directory below, and other directories are the directory where the software corresponding to the additional file is located. After the installation is complete, exit.
(2) Application of client-end installation
The installation of the client is generally after the server installation (because the client's installation is to use the server and resources). The client-end installation file is located in the "C: / Program Files / Microsoft Visual Studio / Vss" directory installed to the server-side "NetSetup.exe", since it is necessary to install on other clients, "NetSetup is required. The directory sharing of the exe "file. Execute this file to complete the software installation of the client side.
2. Configure
(1) server side configuration
A database and user needs to be configured on the server-side machine to establish a corresponding control management system. A database is generally established in a project (or engineering) and establishes several users who should have a database (for management of grading, permissions).
1 database configuration
Click on the installation "program" - "Microsoft Visual Stri 6.0" - "Microsoft Visual Source Safe" - "Visual SourceSafe 6.0 Admin", open the management interface.
Click on the menu "Tools" - "Create Database ...", select the path you want to store in the database (it is recommended to create a directory for the database to specifically use), assuming "D: / vsstest". After the selection is complete, click "OK" to establish a database "vsstest" corresponding to this directory, and the system will give the corresponding prompt information after completion.
Click on the menu "users" - "Open SourceSafe Database ...", open the database selection dialog; click the "Browse ..." button, select the configuration file "srcsafe.ini" in the "VSSTest" directory of the original database, click "Open" Button, then the directory name appears in the available database list name. At this point, click the "Open" button on the right.
Tip administrator changes the password of the super user "admin", click "OK". Open the management interface, it is recommended to modify the superuser "admin" password immediately: Select the user "admin", click on the menu "Users" - "Change Password ...", enter the new password, and confirm (the old password does not need to be input, because the default is Empty), click "OK" to save. After that, it is recommended to change the "guest" user's permissions to make it only read-only privileges (because the user has the same permissions as "admin" users), the operation is as follows: Double-click the "Guest" user, in the pop-up dialog box The "Read Only" check box in the middle is selected, then click "OK". 2 Project security settings
(Receive Front) After entering the management interface, you need to open the user's security setting function (the system is off). Click on the menu "Tools" - "Options ...", open the "Source Options" dialog box, click the "Project Security" tab, you can see the "Enable Project Security" option is unselected, "Default User Rights is also gray. We selected the "Enable Project Security" option and select "Read" on the default user permission below, and click OK to save the modification. After that, after the user is created, the new user's default permissions are "read", which can be detailed in detail according to the role of members in the project (see "4 users and permissions settings").
3 Import of project files
Once the database is typically established, there is no project file, which requires the files under the item to be managed into the database. The following is an example of JBuilder7.
After opening JBUILDER7, create a new project (process slightly; if the project you want to manage exists, open directly), click on the menu "Team" - "SELECT Project VCS ...", in the open dialog box, select " Visual SourceSafe, then click "OK" to confirm, indicating that the version control system to use by the project is "Visual SourceSafe". Click on the menu "Team" - "Place Project INTO VSS ...", in the open dialog box, first select the directory where the database "vsstest" is selected, click "Next", enter "Add" username and password, click "Next" Confirm that the folder and file to be imported into the database (can be done by the default selection recommended by JBuilder7), click "Next", ... until the last step, enter the text box in "Project Name:" to establish it in the VSS system Project Name, enter "Vsstest" here, then click "Finish". At this point, the files in the project project have been imported into the VSS database and include the version control; after adding, deleting, modifying the files in the project engineering, updating the VSS database in time to implement the control of the system version . Detailed operation See the "Use" section later.
4 settings for users and privileges
In order to facilitate grading management of members and their access resources based on different member characters in the project, only the default user rights are set in "1 database configuration", so the members allocated in the project according to the actual situation. Access authority, that is, the user corresponding to each member in the project is established according to the position of the post role. Suppose there are three members in the current project, so three users are built: user, user1, user2, the roles of the project team, the responsible person of the project team, module 1, module 2 responsible. It can be seen that the project team leader should have full permissions; the responsible person of the module 1 should have full authority to the module 1, and the module 2 is read, the responsible person of the module 2 should have full permissions to the module 2, and read the module 1 Permissions can be (here, the modules 1 and modules 2 are assumed corresponding to two different directory module1 and module2). The specific user rights are set as follows: Open "Visual SourceSafe 6.0 Admin" and enter the management interface. Click on the menu "Tools" - "Rights By Project ...", open the project and the corresponding user rights management interface. Since the user rights have passed (ie: subdirectory inheriting the permission of the parent directory), just set the top-level directory to be controlled (if there is special needs, you can set it separately), so as not to go Trouble in layers. The user permissions in the current project are set as follows:
Select the root directory "vsstest", select the user "user" in the right user list, currently its corresponding permissions are only "read", because it is the project team leader role, so the other three "Check Out / Check IN", "Add / rename / delete", "destroy";
Select the user "user1" on the right and select the directory "module1" on the left. Since the USER1 has full permissions on the module 1, the following three "Check Out / Check IN", "Add / Rename / Delete", "DESTROY" Select;
Select the user "user2" on the right and select the directory "module2" on the left. Since the USER2 has full permissions on the module 2, the following three "Check Out / Check IN", "Add / Rename / Delete", "DESTROY" Select.
At this point, the user and its permissions in the system have been basically set. Administrators can make corresponding changes to users and their permissions settings according to the actual situation in the project.
(2) Client-end configuration
Take user "user1" as an example. Open "Programs" - "Microsoft Visual Studio 6.0" - "Microsoft Visual Source Safe" - "Microsoft Visual SourceSafe 6.0", open the login window, enter "User1" after the username, the password input box is entered as "User1 "Set the password, select the new database" Vsstest "in the Database box, click" OK "to open the Visual Source Safe client management interface. Here, you can view the current status of the project in the open database and make relevant management of the database in the case of permission license.
3. use
The following is combined with JBuilder7 to illustrate the use of VSS and routine management.
(1) Engineering file and VSS connection configuration
After opening JBUILDER7, open the project corresponding to your project. Note: To modify the user and password of the login VSS according to the current operating user (the members in the current project need to be modified to make different people use their own login user name). Click "Team" - "Configure Visual SourceSafe", enter the corresponding username after "UserName", "password", enter the corresponding password, click "OK" to determine. After all settings are complete, the current project has been developed under JBuilder 7 has undergone VSS control management.
(2) JBUILDER7 and VSS interaction command description
When the software developed in JBuilder7 is incorporated into the VSS control, each member in the project is developed in accordance with certain processes:
1 First, execute the menu "Team" - "Commit Browser" to synchronize the latest version in the database;
2 When adding a new page, execute "Add ..." to synchronize the new file into the database and write the corresponding annotation text to facilitate unified management;
3 Before modifying the file, "Check Out ..." should be executed to synchronize the latest version of the file on the database, and make the mark, so that other users can only read and cannot modify the file (this operation is based on the current server does not support multiple users. " "Check Out", this is also a model recommended by the team's development)
4 When the file is to be deleted, "Check Out ..." should be performed in the synchronization of the file on the database, then execute "Remove ...", delete the file from the database, and finally "delete ..." deletes the file.
(3) The current state of the project View
During the development process, you can open the Visual Source Safe at any time to see the status of the current project and make the appropriate processing. Click "Programs" - "Microsoft Visual Studio 6.0" - "Microsoft Visual Source Safe" - "Microsoft Visual SourceSafe 6.0" to open the database "vsstest" as the corresponding user.
Note:
"Administrator" is only a concept of concept, which can be the project team leader;
"
VSS
"Represents version control system software"
Microsoft Visual SourceSafe
"
