Visual SourceSafe Concise Training Tutorial (Introduction)

xiaoxiao2021-03-06  63

As a management tool for version control, although Microsoft's Visual SourceSafe has many things that are not satisfactory, this is also complained. But I think that more use is inconvenient, because it is caused by unfamiliarity of the tool. This tutorial is that the author is adapted according to the VSS online help documentation when examining version control a few months ago. It is said that it is a tutorial, but it is better to say a concise manual because its content covers all the functions of VSS and extracts self-conscious and valuable things, and translates it into Chinese. Among them, there are good suggestions and use techniques, such as: Regular backup of the complete VSS data directory, regularly clear the contents of the temporary directory, try to use a data inventory to put all the files, use virtual rollback (Virtual rollback) instead of ordinary rollback, exclusive sign Use, Cloak operation, etc., not enough.

For branch / share / pin / label, the combination of these functions, the relevant parts of the body and appendix provide a quite good example, demonstrate how to use the flexible use of the features to deal with different development scenarios. When I saw this part of the content, I had a sense of great achievements for a while, and I can't help but think that the original VSS can also be used. I believe that these examples will also have a small revelation and "shock".

In addition, the "VSS command-permission level corresponding table" of the appendix section is the result after the author's finishing. It has it. You can use what kind of feature to users with different permissions, and it will become a glimpse.

I hope this tutorial can help developers and managers who are not very familiar with VSS, and I hope I can take this opportunity to clarify some "prejudice" for VSS :)

Click here to view the Visual SourceSafe Concise Training Tutorial

Directory 1 Description 2 Overview 3 Administrator section

3.1 Maintenance User List

3.1.1 Adding User 3.1.2 Change Password 3.1.3 Creating User List 3.1.4 Deleting User 3.1.5 Editing User Properties 3.2 Managing Database

3.2.1 Analysis Data Contents 3.2.2 Database Package 3.2.3 Clear Temporary Contents 3.2.4 Lock Database 3.2.5 Database Recovery 3.2.6 Using Multiple Databases 3.3 Related Permissions

3.3.1 Transmission 3.3.2 Safety Access Right 4 Ordinary User Part

4.1 General use of engineering, document

4.1.1 Opening / Off Database 4.1.2 Creating a New Project 4.1.3 Add Files, Directory, Engineering 4.1.4 Delete and Recovery Files, Engineering 4.1.5 4.1.6 Rename File, Engineering 4.1.7 Settings Work Catalog 4.2 Check In, Check out, Get, View, and related

4.2.1 Check In Sign Operation 4.2.2 Undo Signing 4.2.3 Get the most recent version 4.2.4 Get Earlier Version 4.2.5 Get and View Files, Engineering 4.2.6 Roll back to previous versions 4.2.7 multi-person sign A file 4.2.8 merge 4.2.9 exclusive checkout 4.2.10 on the project's CLOAK operation 4.3 Branch, Share, Label and PIN operations

4.3.1 Branch / Share Operations for Files and Engineering 4.3.2 gives the file, project designated tag 4.3.3 PIN operation 4.4 Other operations

4.4.1 Extended Keyword 4.4.2 Using Shadow Contents 4.4.3 Performance Optimization 4.4.4 Find File 4.4.5 Setting Password 4.4.6 Write Batch Document 4.4.7 Custom SS.INI and Srcsafe.ini file Appendix

A1 also maintains a corresponding permission level of multiple versions of the A2 VSS of a project

Schedule VSS Correspondence Level

In the table below, the star indicates that the user with this type of authority can use this command.

Function rcadadd ** branch ** check in *** check out *** cloak **** create [1] ** delete ** destroy * Difference **** get Latest version **** history **** Label ** links **** merge [2] *** merge **** move [3] ** move * Pin *** purge * recover ** rename ** rollback * share [4] *** Share ** undo check out *** SET WORKING FOLDER *** [1] Here, the user must have a Class A permissions to the Parent Project. [2] Here, the user must have Class C permissions for the purpose of PROJECT, while there is R-class permission to the original Project. [3] Here, the user must have a Class A permissions to the destination Parent Project, and there is a D-class permission to the original Parent Project. [4] Here, it means that the user must have Class C permissions on the original Project, and there is a Class A permission to the destination Project. - MORNING --HTTP: / /MORNINGSPACE.51.NET/, MOYINGZZ@etang.com

转载请注明原文地址:https://www.9cbs.com/read-106006.html

New Post(0)