VSS uses the Guide __ version control tools

Source: Internet
Author: User


VSS is a version control tool. Its operation is relatively simple, easy to use, but also to meet the needs of the company, so VSS in our company has been very good application. Refer to the VSS Usage Guide for specific actions by VSS. Here is a brief explanation of some of the rules for VSS operations.


Whether it's a program source code, a resource file, or other material, we always want to get the latest version from VSS and compile it locally without any modifications. Of course, the resources on the VSS server may not be under one project (project), and it is possible that the resources needed for the project are applied from another project. So, require each project to have a list of resource insinuations.


Here's how to manage our resources in VSS with the engineering unit. Engineering is a functional module. We already have some of the following works:

$/Company Products/wap Product catalogue are:

ThirdParty Project: This project focuses on a number of third-party packages, such as Apache, Sun, database connections, and so on.

Ptree Project: This project is mainly put on the company's own development of some packages, generally in the project as a unit. such as common package, and some resource documents of the project.

Project-doc Project: The project is decentralized to all documents of the company.

$/Company Products/wap product/code directory are:

Common project: The project contains some APIs that the company often needs to use, as well as public files for build tools.

List of resource mappings

A list of resource mappings is a descriptive file that describes the mapping of a resource file on a server to a local machine directory.

A project cannot possibly be independent, it must be used for other engineering resources. Without a list of resource mappings, no second person would know what resource files were needed for the project except for the creation of the project. Although, these resources can be put under the project, but this is a waste (the most important is the waste of hard disk resources), and for future management will cause a problem (such as Third-party package upgrade, if each project uses its own Third-party package, then request to upgrade, It is likely that some projects have already used a new Third-party package, and some projects are not using new, so when the product integration, it is likely to cause such or such unnecessary trouble.

So, the list of resource mappings here is very important, and each employee has to carefully write the list of resources.

The following are some of the columns in the list of resource mappings.

List of resource mappings for ThirdParty projects:

$/Company Products/wap Products/thirdparty E:devthirdparty

is very simple. Because only one sentence can be described clearly. This means mapping all files in the "$/company product/wap Products/thirdparty" directory on the VSS server to the "E:devthirdparty" directory of the Local machine, and when performing the get Latest version operation, The project ThirdParty will be copied to the directory E:devthirdparty under the project.

The list of resource mappings for a project is listed below:

For example, there is a project, his name is Demoproject. The address on the server is: $/company product/wap product/code/demoproject. So the mapping list is likely to be this:

$/Company Products/wap Products/code/demoproject/... e:devwapdemoproject/...

$/Company Products/wap Products/thirdparty/jdbc/oracle/class12.jare:devthirdpartyjdbcoracleclass12.jar

$/Company Products/wap Products/ptree/common/lib/... e:/dev/demoproject/shared/common/lib/...

$/Products/wap Product/code/common/build/build.sh e:/dev/demoproject/build/build.sh


Note: It is generally necessary to describe the mapping to which file, not the entire directory. Unless it's necessary. Above the ... Indicates that all files in this directory are mapped.

Basic Operations

Get Latest Version

is to synchronize the resources on the server to the local. The first time, you will be reminded to set up a local directory, that is, set the file mapping relationship, remember: The file mapping relationship must follow the description in the resource map list file.

Check in

is to submit locally modified files to the server. You must confirm one thing before submitting it, we call it code REVIEW. Perform the show differences operation, see where you modified the file, and confirm that the modification is correct. If you have not made any changes or repaired the error, perform the Undo check out.

Check out

Before doing this, verify that your local computer is the latest version of this file and that the file is not being check out by someone else.

When we want to modify a file, we need to check out this file. At this time, the local files will be read-only from the-> property. Make sure that you do not modify the file directly from a read-only property to a writable file locally. Because this way your modifications will not react to the server. When someone else makes a get latest version of the file, it's not the file you modified, it's the original error file.


There are two ways of view, one is direct view: is not the file check out of the view operation. One is to check out the files to the local directory, which is equivalent to the edit operation


The edit operation first will check out the file to the local directory, and the file is readable and writable.

Undo Check out

File check out, or after an edit operation, undo Check out if the modification is useless, if no modifications have been made, or if you do not want to submit the modified content to the server (when the local file is returned to the original version). You must be cautious about this operation.

Show Differences

This action determines where you have modified the file. It will be better than the latest version and the version you modified, and then put the different places in red color to mark out.

ADD New File

Add a new file to the VSS server. You can drag: Drag the file you want to add to a directory on the server, and the file will be added to the directory. See the VSS Usage Guide for specific actions.

New Project

New projects are the most troublesome operation. The most troublesome is to map the description of the list, the work is simple but trivial. We have a one-touch version of the project for your reference.


1 VSS Overview

Versioning is an important aspect of workgroup software development to prevent accidental file loss, allow back-tracking to previous versions, and branch, merge, and manage versions. Source code control is useful in software development and when you need to compare two versions of a file or retrieve a previous version of a file.

Visualsourcesafe is a source code control system that provides complete versioning and configuration management capabilities, as well as security and trace checking capabilities. VSS works on project development and management by depositing relevant project documents, including text files, image files, binaries, sound files, and video files, into the database. Users can share files quickly and efficiently as needed. Once a file is added to VSS, every change is recorded, the user can recover an earlier version of the file, and other members of the project team can see and modify the latest version of the document, and VSS will also record the new changes. You will also find that using VSS to organize management projects makes communication and collaboration between project groups easier and more intuitive.

VSS can be integrated with visual Basic, Visual C + +, Visual J + +, Visual InterDev, Visual FoxPro development environment, and microsoftoffice applications, providing ease of use, Project-oriented version control features. Visual SourceSafe can handle any file type that is created by various development languages, authoring tools, or applications. In advocating the reuse of files today, users can work at both the file and project levels. Visual SourceSafe Project-oriented features enable you to more effectively manage the day-to-day tasks of your team's application development efforts.

[@more @]

1.1 files in VSS

When you want to modify a document, you need to check it out of the database (check out), or tell VSS that you want to edit the document. VSS will take a copy of the document from the database to your working folder (working) and you can modify your document. If another user wants to modify the same document again, VSS produces a message telling him that the document has been checked out (check out), preventing multiple people from modifying the document at the same time to ensure the security of the document.

When you have completed your modifications, you will need to check in the document (check in) VSS. This operation copies the document that you modified from your working folder (working folders) and puts it back in the VSS database so that other users can see the document changes in a timely manner. VSS is able to save all changes to the document and display the latest version, while earlier versions are tracked. VSS's use of reverse Delta technology requires only a small amount of disk space to enable users to get all versions of the document.

If you do not modify the document, you can perform the Undo checkout (Undo Check out) command, and the document will be saved in the state prior to checkout (check out).

If you simply read a document without editing it, you can perform a fetch command, place the document in your working folder, and then choose to view the document to see the latest version of your document.

1.1.1 projects in VSS

Project is a collection of all files (file) that users store in the VSS database. Users can implement the Add (add), delete (delete), edit (Edit), share (share) of a file between projects or within a project. A "project" is much like a common system's folder, but it better supports file merging (merge), Tracking (archive), and Versioning (version control) capabilities.

Files are saved in projects (project) in the VSS database. You do not need to manage the originals of files stored in VSS unless you want to check or compare them with other copies.

VSS provides each user with a copy of the backup file into the working folder (working) for the user to view and edit the file. Although you can view files without working folders, you must establish a working folder if you want to truly work with the document.

1.1.2 version control features of VSS

VSS is able to save multiple versions of a file, including minor changes between file versions. Version control has the following elements:

Group cooperation--by default, a typical file is allowed to be modified by only one user at a time, which prevents the file from accidentally being altered or overwritten by another user. However, administrators can change this default setting to allow multiple layers of files to be checked out. This setting can also prevent excessive, unnecessary changes.

Version tracking--vss the ability to store and track source and other files, as well as previous versions of rebuilt files.

Cross-platform development--in the case of multiplatform development, version tracking is used to maintain core code.

Reuse of code-tracking program benchmarks makes code reusable.

1.1.3 split and share of files

In VSS, you can implement a file that is shared by multiple projects (share). Changes to files in one project can be automatically reflected in other shared items. This is the promotion of code reuse. In properties in the File menu, click Link to view a file's share.

Split (branch) is the process of separating a file from the previously shared project. It allows VSS to implement trace files from different paths.

Note: In other version control systems, branches are implemented by tracking version numbers. For example, the version "" is the Nineth branch of the second revision of version 2.3. VSS implements a trace of the file branch through a distinctly different project name.

Splitting a file breaks a shared connection, making the files in this project irrelevant to other previously shared projects. Changes to this file will no longer be reflected on other projects. Splits are built in this way: Two files previously had a common history, starting with the implementation split, and their history will be tracked separately by VSS.

When you split a file, link button will no longer show disconnected connections, but you can use path (the properties item in the File menu) to browse through the split history.

A shared (share) file is a connection that creates a file between multiple projects. A split (branch) file creates a different file path between projects.

1.1.4 Working folders (working folder)

VSS is a tool for storing and managing files, but editing and compiling files must be done in a VSS-specified folder. This folder is called a working folder, it can be an existing folder, or it can be a new VSS folder. The VSS browser displays the path to the file's working folder above the file list.

In the VSS system, the working folder is where you really work on the document. When you want to edit or modify a document, you must perform a check out operation on the document (see 3.3.5 Modify and edit the file), VSS copies the document from the project and puts it into your working folder. When you have finished modifying and check in files, VSS copies the files back to the database to record your changes.

Once you check out the file, VSS starts creating and managing your working folder on your local machine.

Each user, every project, or every computer can have its own working folder. If Joe works on the project $/spreadsheet and $/wordprocessor, he has a corresponding 2 different working folders. If Hanna works on the same project, she has her own working folder for each project.

When you set up a working folder for a project, you can use it to place the items in your project that are included in the sub project.

2 Client installation of VSS

2.1 system conditions for installing VSS

Computer/Processor: processors recommend Pentium or more advanced processors for 486dx/66mhz or above PCs.

Memory: Windows 95 or later versions require 16MB RAM (recommended MB), and Windows NT 4.0 requires MB (recommended MB).

Hard disk: Client: Typical installation: 59MB; MB; installation process: 66MB;

Server: Typical installation: 128MB; maximum installation: 141MB;

Additional hard Drive requirements: InternetExplorer: typical MB, max. MB;MSDN: Typical 57MB, max MB

Drive: CD ROM

Display: VGA or more advanced display, recommended SUPERVGA.

Operating system: Microsoft Windows 95 or later or MicrosoftWindows NT 4.0,nt requires service Pack 3 or higher (including ServicePack 3)

Peripherals/Other: Microsoft Internet Explorer 4.01 Service Pack1 (included).

2.2 Install the VSS client from the network

Open the Network Places Properties dialog box for the local computer;

Click "Configure" button;

Set the properties of the Microsoft Network user to: Log on to the Windows NT domain with the domain name planning;

Add TCP/IP, NETBEUI, ipx/spx protocol;

Restart the computer and log in to the "planning" domain; Note: The login password set by the administrator for each NT user is "111", and the computer prompts the user to modify the password the first time they log on.

Look for the server "Vssdata" from the "Planning" field in My Network Places;

Open the shared "VSS" folder and double-click "Netsetup";

Follow the installer prompts to start the installation.

3 basic usage operations for VSS

3.1 log on to VSS

Click the VSS icon or run Visualsourcesafe 6.0 from the Program menu to open the VSS browser.

If the user logs in with a VSS password that is consistent with the password for the login planning domain, the system will no longer prompt for a password to enter the VSS database, and the user will be prompted to enter the VSS login password if the user sets the password for VSS to be different from the password for the login planning domain. For details on how to modify the VSS user password, see "3.2.14 Modify User Password".

3.2 VSS Browser

When you open VSS, if you set a password, it prompts you to enter a password. If you do not set the password, you can see the browser directly. In a browser, you can browse your database, view a list of items, display file statistics, execute commands on files and projects, and so on. The topmost title bar of the browser is the database you are currently connected to. VSS uses symbols to provide information about files and projects.

Below the menu bar is a common toolbar with a number of buttons for common commands that can help you quickly perform operations on files.

In the project bar, displays a list of items, including information about special items. The file bar displays a list of all the files for the current project. The result bar shows the results of the action you are currently performing.

3.3 VSS Basic Operations

3.3.1 Create a new folder

Select the item (parent folder) where you want to create a new folder;

In the File menu, select Creat Project;

Write the name of the folder you want to add, as well as add notes to the new folder in the Comment column;

Click OK.

3.3.2 Add Folder

Select the item you want to add a folder to (parent folder);

In the File menu, select Add Files;

In the Folder list, select the folder you want to add;

Click Add, and you can make a simple remark on the folder you added to the comment bar.

If you want to add together with subfolders, select recursive;

Click OK to successfully add a folder with notes. Or click Close to exit the operation, return to the AddFiles dialog box, and click Close.

3.3.3 Add Files

1. Add files using the Add command

Select the folder you want to add the file to;

In the File menu, select Add Files;

In the file list, select the file you want to add, and if you want to add more than one file, you can use the CTRL key or the SHIFT key while selecting multiple files;

Click Add, and you can make a simple remark on the folder you added to the comment bar.

Click OK.

2. Add a File/folder using the Drag method

Open the VSS browser to resize it so that Windows Explorer can be displayed;

Open Windows Explorer and resize so that two browsers can be displayed at the same time;

Select the file or folder you want to add from Windows Explorer;

Drag the file or folder you selected and put it in the admin editor on August 13, 2009 to edit the article.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.