If you need to copy, spread, please attach this statement, thank you. Original source: http://morningspace.51.net/ ,moyingzz@etang.com
1 description
First, this tutorial provides several use instructions for Visual SourceSafe 6.0 for different use objects, including Visual SourceSafe administrators and ordinary users, and want to know how to use Visual SourceSafe to control managers. Administrators or ordinary users can check this tutorial if you have anything you don't know if you don't know how to do it, or you don't know how to do it, or you don't know much about some operations. Second, the "administrator part" of this tutorial is the administrator must read. If the administrator also serves as a normal user role in addition to its own responsibilities, please refer to the "Ordinary User Part" in the tutorial. As a general ordinary user, just read the "ordinary user part". Third, the operation listed in the tutorial, plus star, is an advanced usage, and the rest is Basic USAGE. The so-called basic usage means that some operations are often used frequently, or is more simple to use. The so-called advanced usage means that there is not much frequency, or more important, or more useful. 4. The content of this tutorial is selected and adapted from the Visual SourceSafe 6.0 English version of the online help, and many important information is extracted, and the content that is easy to ignore and a number of precautions. Some basic contents (mainly referring to the use of certain basic operations) Simply list entries, please see the details of these entries, please check the connection between the online help, you can search in online help after listed by these entries. To related content. 5. This tutorial does not involve the explanation of the Visual SourceSafe graphical user interface operation, check the relevant section of the online help for the specific operation steps for the specified function. Related content can be searched in online help by listed in this function. Sixth, in other Visual Studio products (for example: Visual C ) can integrate Visual SourceSafe, this tutorial does not involve how to use the Visual SourceSafe function in other integrated development environments, this part of this part is primarily for ordinary users. The understanding of these contents will become easy after reading the tutorial. In addition, some operations are more convenient in the Visual SourceSafe environment.
2 outline
Visual SourceSafe (hereinafter referred to as VSS) is a version control management tool. It helps you effectively manage projects by depositing various types of files (including: text files, image files, binary files, sound files, video files, etc.) into their internal databases (Project, the concept of engineering in VSS) Please see below). It allows you to share the same set of files between multiple projects; you can add a file to the database so that other related personnel are used; any changes to files will be recorded so that you can restore it to the file at any time. An old version. VSS engineering organizations make team collaborative development easier and intuitive. A project is an arbitrary type file stored in the VSS database, a project similar to a directory in the operating system, but VSS provides more functional support for version control, history, file merge.
3 administrator part
3.1 Maintenance User List (Maintain The User List)
3.1.1 Adding a user (Add A User)
If you are here, please refer to the online help.
3.1.2 Change Passwords This is omitted, please review the online help.
3.1.3 Creating a list of users (CREATE A User List)
If you are here, please refer to the online help.
3.1.4 Delete Users (Delete a User)
If you are here, please refer to the online help.
3.1.5 Edit User Attributes (Edit User Attributes)
If you are here, please refer to the online help.
3.2 Management Database (Manage the Database)
3.2.1 Analysis Data Directory * It is recommended that you regularly back up the full VSS data directory (see Database Package). The VSS data directory contains database information with all the projects and files. Due to certain faults of the network or operating system, the files in the VSS may exist errors and inconsistencies, and the Analyze VSS DB tool is used to find and fix these issues. Before running the tool, you need to lock all users and ask them to exit the VSS, and the user can keep the file checklist when a database is locked (see Lock Database). It is recommended to run an Analyze VSS DB tool twice, the first repair error, whether the second verification still does not have a fixed error. The specific location of the data directory is specified by the Data_Path initialization variable in the srcsafe.ini file (see custom SS.INI and SRCSAFE.INI files).
3.2.2 Database Packaging (Archive Databases) *
You may need to back up the VSS database regularly, or some part of the database. The VSS Administrator tool provides this feature. it can:
Save the disk space of the VSS database server. Accelerate the speed of display history. It is convenient to pass files and projects between multiple VSS databases, and keep history is complete and free. Back up all or part of the VSS database content and compress into a file. 3.2.3 Clear Temperature Folder (Clean Temporary Folder)
VSS is usually placed in a temporary directory at runtime and deleted it before exiting. For some reason, such as abnormal restarts, the temporary content may remain in the directory. As an administrator, you have a responsibility to regularly clear the content of the temporary directory. Every few weeks, when no user runs VSS or VSS Administrator, clear the contents of the temporary directory. The specific location of the temporary directory is specified by the TEMP_PATH initialization variable in the srcsafe.ini file (see custom SS.INI and SRCSAFE.INI files).
3.2.4 Locking Database (Lock A Database)
The database lock function will not automatically lock the user currently logged in, and you should log in to the user to exit the VSS before the database is locked. Before re-allowing users to use VSS, you need to unlock the database. 3.2.5 Database Recovery (RESTORE DATABASES)
If you are here, please refer to the online help. 3.2.6 Using multiple databases (Work with multiple data) *
In default, VSS places all files in a database. If possible, try to use a data inventory to put all files, which is better than multiple data inventory, because: You cannot share (Share) files between multiple databases (see BRANCH / Share operation on files and engineering). It is more difficult to set the contents in multiple databases, and you need to use the VSS Administrator's Archive function (see Database Package). For security considerations, VSS user information, including password, is stored with data. If you want to split information into multiple separate databases, VSS is set to a database in a database. If possible, try to use a data inventory to put all files, which is better than multiple data inventory, because: You cannot share (Share) files between multiple databases (see BRANCH / Share operation on files and engineering). It is more difficult to set the contents in multiple databases, and you need to use the VSS Administrator's Archive function (see Database Package). For security considerations, VSS user information, including password, is stored with data. If it is sure to split information into a plurality of separate databases, this information store will bring great convenience, but you must add users separately for each database. 3.3 Topics related to privileges 3.3.1 Transfer of permissions (Rights Propagation)
When you add a new user, when you set the user's permissions for a project, you will build an ASSIGNMENT in the VSS database. The Assignment will pass down the project tree until you encounter another Assignment.
For example: For the project "$ /", you specify add permissions for User A (see Secure Access Permissions), and for project "$ / Sample", you did not explicitly specify permissions for users, the user will work "$ / Sample "automatically has Add permissions. When you specify the READ permissions at the project "$ / Sample / BusinessObject", you will prevent the downward transfer process of early ASSIGNMENT, so user A is the project (refer to "$ / sample / businessobject") and its sub-engineering Only have read permissions.
When you add a user for the first time, the permissions given by the project "$ /" are determined by the Default Permissions, and the default permissions are defined by setting the contents of the Project Security property page in the VSS Administrator. You can change all users' default permissions by modifying the contents of this page.
3.3.2 Safety Access Rights (Security Access Rights)
3.3.2.1 Default Security Settings
After installing VSS, the default security settings will be enabled. You can use customized ways to enable some users with specific permissions for certain projects and some VSS commands.
The default security setting is simple. When adding new users, you only have two levels of access to access:
Read-Only Rights: The user can view anything in the VSS but cannot be changed. Read / WRITE RIGHTS: The user can view and modify anything in VSS.
If such access rights level is sufficient to cope with everyday use, there is no need to enhance the level of security control. All VSS security management is done in VSS Administrator. Any user who can run the program can change any of the characteristics of the VSS, so it is best to use the program only.
3.3.2.2 Higher level security control
In VSS, the security control of the project is implemented by developing user access rights. Each project can only be accessed by users with corresponding permissions, each command can only be used by users with corresponding permissions. Permissions can be customized through VSS Administrator to achieve higher level security control.
The following is a list of VSS permissions, each of which has all permissions before this permission. For example: a user with Check Out permissions, will also have read permissions. (See Appendix A2: Correspondence Level of Commands in VSS)
Permission Description Read (R) Similar to read-only permissions in the default security setting Check Out (c) You can modify add (a) using the check out / check in / undo check out, etc., add / delete / label / Rename and other commands modify DESTROY (D) You can use DESTROY / PURGE / ROLLBACK to implement permanent deletion operations
(Continued)
