When the file in source safe is newer than the file content of the local machine, select this file in source safe, then get the latest version command, and then check out according to the default options;
When the contents of both are the same, follow the default options.
Note: The concept of file lock is used in source safe. When a file is checked out by others, others cannot check out this file; if the file lock is invalid, you can check whether the Visual SourceSafe 6.0 Admin-tools-general-allow multiple checkouts option is selected. Only when check out modification file is completed, you must check in to ensure that the files in source safe are up to date.
Remember that check out will make the code writeable to yourself and read only to others. Please only check out the part that you need to modify by Check Out, otherwise the members of the same group will have to rest when you are working.
(6) Upload files to server operation
We must use the check in command to ensure that the local file of source safe is synchronized, and check in appears in pairs with check out. Its function is to update the check out file in source safe with local files.
For specific operations, select the file in the check out state in source safe. Right-click to select check in and a dialog box will appear: under default state, its two check boxes are in the non-selected state. The Keep checked out option can automatically check out again after check in, which is equivalent to omitting the next check out operation; the remove local copy option can delete the file with the same name in the working folder on the local machine while checking in.
Generally, you can follow the default options. After Check in successfully, the source safe and the local file are exactly the same, and the local file becomes a read-only file. When you want to modify the file again, execute the check out operation, and the file attributes of the local machine will automatically become writable. Remember to check out after check out, otherwise the consequences will be like not saving after writing the file.
Be sure to ensure that your document is correct and can be compiled before Check In, otherwise it will make it impossible for others to compile and the entire project cannot be debugged.
(7) undo check out operation
When a file is checked out, if you want to undo this operation, you can use the undo check out command. Operation steps: Select the file in the check out state, right-click and select undo check out.
When the file in source safe is exactly the same as the local file, there is no prompt message and the file returns to normal state.
When the file in source safe and the local file is not exactly the same, a prompt window appears, and the dialog box local copy includes three options:
After the replacement option is selected, the system will ask whether to overwrite the information. If you click yes, it will overwrite the file on the local machine with the last version of the file on the source safe. If you select no to retain the content of the file on the local machine, the file on the source safe is the content after the last check in. At this point, the two files may differ;
The leave option retains the content on the current computer. The file on source safe is the content after the last check in. The two files may be different;
The delete option deletes this file on the local computer.
After selecting an option, click OK, the file returns to normal state.
(8) edit operation
The edit command is a combination command, a combination of commands that check out first and then modify. It should be noted that after executing the edit command, we modified the file, but the files in source safe are not synchronized. We still need to check in to synchronize the local file with the files on source safe.
(9) View the historical content of the file
Method to select this file, right-click and select show history. After a dialog box appears, a form pops up after selecting OK. We can see all versions of this file. To view a certain version, you can select the VIEW button. If you want to download a previous version, you can click the get button.
(10) Permissions about source safe
By default, project security management is run in a simple mode, that is, users have only two types of permissions to the operation of the project, one is read-only permission and the other is read-write permission. To enable Advanced Mode, select this option in Visual SourceSafe 6.0 Admin-tools-project security-enable project security.
The permissions of source safe are divided into 5 levels:
No permission level: File not seen
read level: can browse files by yourself, you can use the get latest version command
check in/check out level: The file can be updated, but the file cannot be deleted
delete level: files can be deleted, but these files can still be restored through certain commands.
Destroy level: You can completely delete files, but you cannot recover them after deletion.
Setting permissions for users is generally done by software configuration administrators in Visual SourceSafe 6.0 Admin.
Permission management is to manage the relationship between operation permissions between users and project directories. Therefore, there are two management methods. One is to manage permissions with the project directory as the main line, and the other is to manage permissions with the user as the main line.
To manage user permissions with the directory as the main line, click the tools-right by project… menu to pop up a dialog box to manage user access rights of the project.
If the user permissions are used as the main line, you should first select a user in the user list at the bottom of the main interface, then click the rights assignments for user… menu to pop up the dialog box. The user's access rights to each project directory of the database are listed below. If accessing a project is not listed on the list, it means that the permissions of the project are inherited from the previous directory. As long as you click a directory, you can edit the user's access to the project directory.
Permission copying is to directly copy one user's permissions to another user. Administrators can implement it through the copy user right… menu.
(11) Changes about password
Password is generally assigned by the software configuration administrator. If we need to modify the password, we can modify it under tools-change password.
One thing to note is that when your source safe password is the same as Windows password, start source safe and there will be no dialog box prompting you to enter your password. This is Microsoft's usual style. This shadow can also be found under the SQL server database management system, because Microsoft believes that the password of Windows should be higher than that of other software. Since you can enter Windows with the same username and password, you have the right to use the same username to enter other software.