VSS Server Installation configuration (a complete VSS server configuration article)

Configure VSS Server Installation

The company's product is about to be released. We need to use VSS for integration testing and repost an article about VSS to share with you.

VSS is called visual source safe. As a member of Microsoft Visual Studio, it is mainly responsible for managing project files and can be applied to almost any software project.

The source code version control mechanism is one of the essential management mechanisms in modern software development. It is usually implemented by the source code management (SCM) systems or version control systems. Version Control plays an important role in software development as follows:

1) As a code repository, it effectively manages the source code and documents of different versions in software development. It occupies a small amount of space and facilitates the acquisition of code and documents of various versions.

2) effectively coordinate access to source code in the development team (different version control software adopts different coordination policies ).

Common version control software include clearcase, CVS, PVCs, and Microsoft Visual sourcesafe (VSS ). The following is a brief introduction to visual sourcesafe 6.0, which is the most common development platform for Windows.

Running Environment

The typical environment for using VSS for development on Windows is based on the C/S architecture, that is, each developer of the development team uses development tools (such as Vc) on their respective Windows platforms) each module in the development project is configured with a dedicated server to centrally control the documents and code in the development process. The server and the developer's client are respectively equipped with the VSS server and client program.

Install

Vss6.0 Server Installation

Step 1: Put CD1 of visual studio6.0 into the CD-ROM, automatically enter the installer, and select the second item "server applications and tools (add only )";

Step 2: In "server setups"'s "server components", select "register a l source safe server", click "Install", and add "CD2" as prompted;

Step 3: Follow the prompts in Installation Wizard to continue the installation process. Select the installation path until you are prompted to restart to make the newly installed program take effect and restart the computer.

Install the vss6.0 Client

After the vss6.0 server is installed, you can install the client software under the guidance of the VSS administrator. Because we are in a Windows environment subnet, each PC client can access the VSS server through a network neighbor. After the VSS administrator instructs the user of the vssclient software installation program named netsetup.exe (in the VSS Server Installation Directory), the user can directly find the program in the network neighbor through the resource manager explorer and double-click it to run it. After netsetup.exe is started, install the VSS client. In the prompt box, enter the user name and working group name, select the installation path of VSS, and click the installation icon to go to the actual installation step, future work will be automatically completed by the system.

Instructions for use

When using VSS, you must follow the lock-Modify-Unlock process instead of the copy-Modify-merge process (such as CVS ), that is, the developer first needs to modify the source code and documentation from the master backup file of the VSS server to the local and lock the source code and documentation on the server (except in the case of multi-Checkout ), after the modification is complete, checkout is sent to the server and the files on the server are unlocked. The server centrally controls all source programs and documents.

Concepts involved in VSS usage

1) A Project is a group of files (of any type) in VSS. files can be added, deleted, edited, and shared between projects. A project has many similarities with the operating system folder, but it better supports file merging, history, and version control. All files exist in the VSS database project, and developers cannot work on the master backup file of the server in VSS (except for checking and comparing versions and other special circumstances) instead, VSS provides each Member with a copy under their working directory (workfolder) for work. Although you can view a file without a working directory, to really work under VSS management, you must create a working directory.

2) The working directory (workfolder) is the place where the user debugging and modifying the project file. When the user Checkout the file, VSS will copy the file to the user's working directory, when the user modifies the file and checkin it, VSS copies it from the user's working directory back to the VSS database. When a user performs checkout, VSS automatically manages his working directory, such as creating necessary subdirectories. The working directory can be created or modified at any time.

3) version tracking. VSS provides version control and history services, and older versions of programs and documents can be re-obtained for Bug Tracking or other purposes. VSS uses a date/time stamp to record when a file is checkout or modified. It has three methods to track the file and project version:

Version: this is an internal digital maintained by VSS, and the user has no control over it. Each file and project version has a version number, which is always an integer and increases progressively.

Date/timestamp: It indicates when a file is last modified, or when a file is checkin. VSS supports both 12-hour and 24-hour time formats.

Vss6.0 server configuration and management

After the vss6.0 server is installed, you can configure and manage the VSS server for the development project, which must be completed by the VSS administrator.

Step 1: Create a VSS database for the entire project (when the VSS server is installed, the system has created a default database common ), start visual sourcesafe6.0 admin (start/programs/Microsoft Visual studio6.0/Microsoft Visual sourcesafe/visual sou rcesafe6.0 admin). In the dialog box that appears, click Create Database in tools... the dialog box appears. Select the path of the new database, for example, create MyApp database, and click OK. The system will complete the creation.

Step 2: create a user for the newly created database (for example, MyApp). First, open the database, click users/Open sourcesafe database... in the drop-down menu, select database MyApp, and open it. Select the menu item Add User... and enter the user name and password. Create other users in sequence. You can set different access permissions for different project folders for different users. There are two methods: 1) Use the features provided by VSS. Select Tools/OPTIONS... In the dialog box, select the ENABLE Project security check box on the Porject Security Attribute page and select Tools/rights by project... Or tools/rights assignments for user... 2) use the cacls command of the Windows operating system.

Step 3: Create a project in the new database. Start Microsoft Visual sourcesafe6.0 (start/programs/Microsoft Visual studio6.0/Microsoft Visual sourcesafe/Microsoft Visual sourcesafe6.0). In the dialog box that appears, click Open sourcesafe database in the drop-down menu file ..., in the displayed dialog box, select a database (for example, MyApp), double-click it, or press the OPEN button to open the database. A project is a set of related documents or a collection of files, VSS allows you to store and organize your projects in any hierarchy. In the VSS database, you can create one or more projects. Click the Create Project command in the File menu ..., create a project, such as myproject. After creating a project named myproject, you need to add a file to myproject. Click the add files command in file. In the displayed dialog box, select a file or directory, click Add to add them to myproject.

At this point, the configuration of the VSS server has been basically completed, the database and project have been created, and the corresponding users have been created for them, in this way, you can directly log on to the VSS server on the client for development under the VSS Control Management.

Note: the directory structure of the server master backup file should be determined before project development and approved by all developers. In actual use, if the directory structure of the master backup file on the server is unreasonable or some files need to be deleted temporarily, the VSS Administrator is responsible for centralized processing.

Use of vss6.0 Client

The following describes how to use the VSS client using a specific instance of the lab data warehouse project.

Step 1: log on to the VSS server. Start the Microsoft Visual sourcesafe6.0 client (start/programs/Microsoft Visual studio6.0/Microsoft Visual sourcesafe/Microsoft Visual sourcesafe6.0). The following logon window is displayed;

Click Browse... Button. The following dialog box is displayed;

Then click browse... Select the directory (shared directory on the dbgroup server, and enter VSS/VSS respectively if you are prompted to enter the account and password of the dbgroup server );

Click the OPEN button and then click OK and open in the following two dialog boxes;

Return to the logon dialog box;

Enter the user name and password specified by the Administrator to log on to the VSS server.

Note: different user and password settings have different access permissions for different directories (projects.

Step 2: If you log on to the VSS server for the first time, you must set the working directory first. Otherwise, you cannot perform the checkout operation.

Shows how to set the working directory. Right-click the folder of the relevant module and choose set working folder ...;

In the displayed dialog box, select the working directory you set and click OK;

Note: After the working directory is set, all files on the server are put into the working directory after checkout. Therefore, the working directory on the local machine should be protected and cannot be deleted and moved at will.

Step 3: Go to the local working directory for the checkout file. Right-click the relevant folder and select Check out ...;

The checkout dialog box is displayed as follows. After you click OK, all the files and subfolders in the directory are checkout to the local working directory and the files on the server are locked in red, other users cannot checkout this folder (the server is set to not allow multicheckout ).

Note: Check the recursive check box to ensure that all subfolders are checkout.

Step 4: Modify and debug the files in the local working directory.

Step 5: Check the file checkin in the working directory. If you do not change the modified file checkin, the modifications to the file in Step 4 cannot be reflected in the master backup of the project file on the server, in addition, it is very likely that the local file will be overwritten by the old version after the next checkout. In the VSS client window, right-click the folder to be checkin and choose check in ..., In the pop-up checkin dialog box, click OK. Then, the files in the local working directory are checkin to the server, and the files on the server are unlocked (black ).

Note: Check the recursive check box to ensure that all subfolders are checkin.

Suggestion 1

In actual use, the developer or administrator has the responsibility to regularly or irregularly label the source programs and documents on the server to facilitate management of the source program and historical document versions. VSS can easily obtain historical versions based on the label (other methods are available to obtain historical versions. We recommend that you use the label method in this article ).

Add a label. Right-click the directory (project) to add a label and select label ...;

In the set label dialog box, enter the label name and related comments, as shown in;

If you want to obtain a previous version, select the corresponding directory (project) and select Show history ..., Select the check box as shown in and click OK;

In the following dialog box that appears, VSS lists all the postmaster labels, selects the corresponding labels, and then click the get button. The corresponding version of the label will be checkout to the local working directory. For other buttons, see help;

Suggestion 2

Developers should not arbitrarily change the directory (Project) structure on the VSS server, do not add or delete files in the directory (project), and do not randomly access others' directories (projects) and files. If the directory (Project) structure on the server needs to change, contact the administrator.

Suggestion 3

Strictly abide by the VSS usage rules to prevent loss of programs or documents due to misoperations. If both users need to modify a unified directory (Project) or file at the same time, perform serial processing instead of multicheckout to reduce the chance of errors.