|
Relevant documents of software testing, test code, and automated testing program code must be included in the configuration management library as configuration items. Vss is a simple and practical tool. We hope that you can use vss properly during testing. 1 VSS Overview
Version Control is an important aspect of Working Group software development. It can prevent accidental file loss, allow reverse tracing to earlier versions, and branch, merge, and manage versions. When software development and you need to compare two versions of files or retrieve files of earlier versions, source code control is very useful.
Visual SourceSafe is a source code control system that provides comprehensive version and configuration management functions, as well as security protection and tracking and inspection functions. VSS saves relevant project documents (including text files, image files, binary files, audio files, and visual files) to the database for Project R & D management. Users can quickly and effectively share files as needed. Once a file is added to VSS, its changes are recorded. You can restore the earlier version of the file. Other members of the project team can also see the latest version of the file, and modify them. VSS also records new changes. You will also find that using VSS to organize and manage projects makes communication and cooperation between project teams easier and more intuitive.
VSS can be integrated with Visual Basic, Visual C ++, Visual J ++, Visual InterDev, Visual FoxPro development environment, and Microsoft Office applications, provides easy-to-use and project-oriented version control functions. Visual SourceSafe can process any file type created by a variety of development languages, creation tools, or applications. When files are promoted for reuse, users can work at the file and project level at the same time. Visual SourceSafe is a project-oriented feature that can more effectively manage the daily tasks in workgroup application development. Files in VSS 1.1
To modify a document, check it out from the database or notify VSS that you want to edit the document. VSS will take the copy of this document from the database to your working folder (working folder), and you can modify your document. If another user wants to modify the same document, VSS will generate a message telling him that the document has been checked out (checked out) to prevent multiple users from modifying the document at the same time, to ensure document security.
After you complete the modification, you need to check in VSS. This operation copies the modified document from your working folder (working folder) and puts it back into the VSS database so that other users can see the document changes in time. VSS can save all changes to the document and display the latest version. Earlier versions are also tracked and recorded. When using the anti-increment technology, VSS only requires a small amount of disk space to allow users to obtain all versions of the document.
If you have not modified the document, you can run the undo check out command to save the document to the status before it is checked out.
If you only need to read a document and do not need to edit it, You can execute the get command, put the document into your working folder, and then select view ), to view the latest version of your document. Project in 1.2 VSS
A project is a collection of all files stored in the VSS database. You can add, delete, edit, and share files between projects or within a project ). A project is very similar to a normal system folder. The difference is that it can better support merge and archive) and version control.
Files are stored in projects in the VSS database. You do not need to manage the original files stored in VSS unless you want to check or compare them with other copies.
VSS provides each user with a backup file in the working folder for users to view and edit the file. Although you can view files without working folders, you must create a working folder to process documents. 1.3 VSS Version Control
VSS can store multiple versions of a file, including minor changes between file versions. Version control includes the following:
L intra-group cooperation-by default, a file can only be modified by one user at a time, which can prevent files from being accidentally modified or overwritten by other users. However, the administrator can modify this default setting to allow multi-layer file check-out. This setting can also prevent excessive and unnecessary changes.
L version tracking-VSS can store source code and other files and track earlier versions to achieve reconstruction of earlier versions of files and other related functions.
L cross-platform development-in the case of multi-platform development, version tracing is used to maintain the core code.
L re-use of code-tracking program benchmarks to make code reusable. 1.4 file splitting and sharing
In VSS, a file can be shared by multiple projects ). Changes to files in a project can be automatically reflected in other shared projects. This advocates code reuse. In properties in the File menu, click link to view the sharing of a file.
Branch is the process of separating files from the original shared project. It enables VSS to track files from different paths.
Note: In other version control systems, branches are implemented by tracking version numbers. For example, version 2.3.9.2 is the ninth branch of Version 2.3. However, VSS tracks the file branches with significantly different project names.
Split the file and disconnect the shared connection, so that the files in this project are irrelevant to other original shared projects. Modifications to this file will no longer be reflected in other projects. The split is created in this way: two files have a common history before, and their history will be tracked by VSS separately from the implementation of the split.
After the file is split, the link button will no longer display the disconnected connection, but you can use the path (properties item in the File menu) button to browse the history of the split.
A shared file is a file connection established between multiple projects. Branch files are different file paths created between projects. 1.5 working folder)
VSS is a tool for storing and managing files, but editing and compiling files must be performed in the folder specified by VSS. This folder is called a working folder. It can be an existing folder or a folder created by VSS. The VSS browser displays the path of the working folder of the file above the file list.
In the VSS system, the working folder is where you really process documents. When you want to edit or modify a document, you must perform the check out operation on the document (for details, see 3.3.5 modify and edit the file). VSS copies the document from the project, put it in your work folder. After you modify the file and check the in file, VSS copies the file to the database again to record your modifications. Once you check out the file, VSS starts to create and manage your working folder on your local machine.
Every user, project, or computer can have its own working folder. If Joe works on projects $/SpreadSheet and $/WordProcessor, he has two different working folders. If Hanna works on the same project, she has her own working folder for each project.
When you set a working folder for a project, you can use it to place the files that include sub-projects and 2 VSS Client installation 2.1 system conditions for installing VSS
L computer/processor: Pentium or more advanced processors are recommended for 48 6dx/66MHz or later PCs.
L memory: Windows 95 or later versions require 16 mb ram (32 MB recommended); Windows NT 4.0 requires 24 MB (32 MB recommended ).
L Hard Disk: Client: Typical installation: 59 MB; 72 MB; installation process: 66 MB;
L server: Typical installation: 128 MB; maximum installation: 141 MB;
L additional hard drive requirements: Internet Explorer: Typical is 43 MB, the maximum is 59 MB; msdn: Typical 57 MB, the maximum is 59 MB
L drive: CD ROM
L display: VGA or more advanced display, super VGA is recommended.
L Operating System: Microsoft Windows 95 or later or Microsoft Windows NT 4.0, NT requires Service Pack 3 or later (including Service Pack 3 〕
L peripheral device/Others: Microsoft Internet Explorer 4.01 Service Pack 1 (included ). 2.2 install the VSS client from the network
1) Open the "Network Neighbor" attribute dialog box of the local computer;
2) Click the "configuration" button;
3) set the "Microsoft network user" attribute to: log on to the Windows NT domain, and the domain name is planning;
4) add TCP/IP, netbeui, and IPX/SPX protocols;
5) restart the computer and log on to the planning domain;
Note: The administrator sets the logon password "111" for each NT user. When the user logs on for the first time, the computer will prompt the user to change the password.
6) Search for the server "vssdata" from the "planning" domain of "Network Neighbor ";
7) Open the shared "VSS" folder and double-click "netsetup ";
8) follow the prompts to start installation. 3. Basic VSS usage 3.1 log on to VSS
Click the VSS icon or run Visual SourceSafe 6.0 from the program menu to open the VSS browser.
If the user logs on to the VSS password is the same as the PLANNING domain password, the system will not prompt to enter the password for accessing the VSS database; if the password you set for VSS is different from the password used to log on to the PLANNING domain, the system prompts you to enter the VSS logon password. For details about how to change the VSS user password, see "3.2.14 change the user password ". 3.2 VSS Browser When you open VSS, if you set a password, it will prompt you to enter the password. If you do not set a password, you can directly view the browser. In a browser, you can browse your database, view the project list, display file statistics, and execute commands to operate files and projects. The title bar at the top of the browser is the database you are currently connected. VSS uses symbols to provide information about files and projects.
Below the menu bar is a commonly used toolbar. There are many commonly used command buttons, which can help you quickly perform operations on files.
A project list is displayed in the project column, including information about special projects. The file column displays a list of all files in the current project. The result column displays the results of the current operation. 3.3 basic VSS operations 3.3.1 create a new folder
1) Select the project (parent folder) for which you want to create a new folder );
2) Select the creat project from the file menu;
3) write the name of the folder to be added, and add remarks for the new folder in the comment column;
4) Click OK. 3.3.2 Add a folder
1) Select the project (parent folder) for which you want to add folders );
2) select add files from the file menu;
3) Select the folder to be added in the folder list;
4) Click add. You can also make a simple note on the comment bar for the folder you added;
5) If you want to add it together with the sub-folder, select Recursive;
5) Click OK to add a folder with remarks. Or click close to exit, return to the add files dialog box, and click close. 3.3.3 Add a file
3.3.2.1 use the add command to add a file
1) Select the folder where you want to add files;
2) select add files from the fil menu;
3) Select the file to be added in the file list. If you want to add multiple files, you can use the CTRL or SHIFT key to select multiple files at the same time;
4) Click add. You can also make a simple note on the comment bar for the folder you added;
5) Click OK.
3.3.2.2 add files/folders by dragging
1) Open the VSS browser and adjust its size so that the Windows resource manager can be displayed;
2) open Windows Resource Manager and adjust the size so that both browsers can be displayed simultaneously;
3) Select the file or folder you want to add from Windows Resource Manager;
4) drag the selected file or folder to the VSS browser. The file is added to the project, and the added folder is used as a sub-project of the project. 3.3.3 view files
1) Select the file to be viewed from the file list;
2) select view from the edit menu to open the dialog box;
3) select View sourcesafe's copy of this file;
4) Click OK. 3.3.4 create a working folder
Check in, check out, undo check out, Get latest version, and merge files (merge branches) you must use the working folder when using commands such. The working folder can be set or modified at any time, and the working folder can be set in the VSS system in two ways.
3.3.4.1 create a work folder
1) Select the file/folder for which you want to set the working folder in the file or project list of the VSS browser;
2) Select set working folder from the File menu to open the dialog box;
3) select or create a folder in the Resource Management list;
4) Click OK.
3.3.4.2 use the check out operation to set the working folder
When you check out a file, if no working folder is set for the file, the system prompts you to create or specify a working folder for the file, you can set the working folder according to the system prompts. 3.3.5 modify and edit a file
1) select edit file from the edit menu to open the dialog box;
2) Select Check out this file and edit it in your working folder;
3) Click OK.
Note: If you have set a working folder for the file, VSS will put a copy of the file into your working folder and open the file for modification and editing; if you have not set a working folder for the file, the VSS system will remind you to set a working folder. You can set a working folder according to the system prompt before editing the file. 3.3.6 move files/folders
3.3.6.1 move a file
You only have one way to move a file: Share the file to the project, and then delete or destroy it from the original project. After the file is moved, the historical information is still valid. However, you cannot use the move command to move a single file.
3.3.6.2 move a folder (Project)
Note: To use the move command, you must first ask the Administrator to set the Add permission for the target project and the destroy permission for the files in the source project.
You can use the move command to locate the sub-folder and move it from one folder to another. This command re-defines the path of the folder to be moved.
This command cannot rename a file. You can only rename the file by executing the RENAME Command. This mobile command does not change the folder content or the history information of its sub-folders. It only affects the historical information of the New and Old parent folders.
Warning when you move a folder, you cannot recreate the earlier version of the parent folder.
To move a folder, follow these steps:
1) Select the folder to be moved;
2) Select move from the File menu to open the dialog box;
3) select the target folder from the list;
4) Click OK. 3.3.7 share a file/folder)
1) select the target project to be shared in the VSS browser.
2) Select share from the sourcesafe menu to open the share dialog box.
3) Select the file you want to share from the file to share list. If the file is not displayed, you can search for it in the project list next to it.
4) Click share.
5) Click Close. 3.3.8 split a file (Branch)
3.3.8.1 split shared files
1) Select the file you want to split in the browser;
2) Select branch from the sourcesafe menu to open the split dialog box;
3) Fill in comment remarks;
4) Click OK.
3.3.8.2 split and share files in one step
1) Select the project to be branch/share in the VSS browser;
2) Open the share dialog box in the sourcesafe menu;
3) Select the file to be shared from the file to share list. If the file you want is not displayed 3.3.9 delete/restore a file or folder
To remove a file from VSS, you must first determine whether to move the file from the project or the VSS database. You must also determine whether to delete the file, but whether to restore it or permanently destroy it.
There are three ways to remove files from the database in VSS.
3.3.3.9.1 Delete)
Remove files from the project. The file still exists in your VSS database and other projects that share the file. You can restore it. This command is also applicable to projects.
1) Select a file or project;
2) Select the DELETE command from the File menu;
3) Click OK.
3.3.3.9.2 damage (destroy)
The delete dialog box contains the destroy permanently option. Once you select it, the file or project will be removed from the VSS database and you cannot restore it. In addition, when the destroy and destroy permanently commands are used to share a file, they only apply to the current folder. Other shared folders still keep the file, and the file is still saved in the VSS database.
1) Select a file or project;
2) Select the DELETE command from the File menu;
3) Select the destroy permanently option;
4) Click OK.
3.3.3.9.3 purge)
This command permanently removes the file or project you have deleted, but does not destroy it. You can use this command to clear all the content in your file or project, but cannot restore them.
1) Select a project in the VSS browser;
2) Open the Properties dialog box of the File menu and press the delete button;
3) Select the file name to be cleared from the list;
4) Click purge;
5) If you want to continue, click yes in the prompt bar provided by VSS. 3.3.10 view historical information or earlier versions of a file/folder
The detailed information of each file is stored in the historical information. In the history dialog box, you can not only view the version information, remarks, and history of the file, but also obtain an old version of the file.
Note: Only files can be checked out from history information, while folders (projects) cannot be checked out from it.
You can also perform get, check out, diff, pin, unpin, roll back, And reprot operations in the History dialog box.
To view historical information:
1) Select show history from the tool menu to open the history options dialog box;
2) Click OK. 3.3.11 get the latest file version
1) Select the file you want to operate on, or multiple files or a project;
2) Select get latest version from the SourceSafe menu;
3) If you have not set a working folder in advance, VSS will prompt you whether to set a working folder, click OK to set a working folder;
4) if you have determined the options, VSS will display the get latest version dialog box, and you can get the latest file backup from the current project, it is placed in your work folder. 3.3.12 obtain an earlier version of a file
1) Select the file you want to view;
2) Select show history from the tool menu to open the history option dialog box;
3) Click OK to open the history dialog box;
4) Select the version you want to view;
5) Click get to open the get dialog box;
6) If you have not set a working folder beforehand, VSS will prompt you whether to set a working folder, click OK to set a working folder;
7) Click OK in the "retrieve" dialog box. The file version Backup will be transferred to your working folder from the current project. 3.3.13 Change User Password
Use the change PASSWORD command to set or change your password. To change the password, you must first know the current password. If you forget your password, contact the administrator.
Upon logon, VSS will prompt you to enter the password to confirm your identity. If the user name set for you by the Administrator is the same as your network name, VSS will no longer prompt you to enter the password.
Note: Your VSS password can be the same or different from your operating system password. It does not replace your operating system password.
How to change the password:
1) Open the change password dialog box from the tool menu;
2) enter your current password in the old password box;
3) enter your new password in the new password box;
Note: The password can be 1 to 15 characters in the form;
4) type a new password in the confirmation box;
5) Click OK. 3.3.15 open/close a database
If you use VSS, your files and projects will be stored in a database. It securely stores your information and provides you with important historical information and version tracking. To create a new database, contact the VSS administrator.
3.3.15.1 open an existing database
To run your VSS, you must connect to the database that stores your files. This step is usually automatically completed by VSS unless you want to select another database. If the database has not been installed, contact the administrator.
1) select Open sourcesafe database from the File menu to open the dialog box;
2) Select a database from the Database List;
3) Click Open to open the database.
3.3.15.2 shut down the database
You can only work in one database. Therefore, to close a database, you only need to open another database. |
