VSS often makes mistakes

1. Get the latest version of the desired file "Get latest version" from the server. Others say it is an executable version, but I cannot compile it normally?

Cause:

In this case, it is very likely that your local disk retains the old files that have been deleted from the server. When you get the latest version from the server, the system only updates files of the same name locally and on the server, and does not delete useless local junk files. The old junk files are kept in the same folder, and the latest files on the server coexist with local junk files, causing the system to fail compilation.

Solution:

If you can determine that the number of files in the server is the same as that in the local folder, you can directly use "Get latest version" to get the latest version of the file from the server for use;

If you cannot determine whether the number of files on the server is the same as that on the local folder, change the name of the local folder first, and create a folder with the same name as the server, use "Get latest version" to get the latest version of the file from the server. Make sure that the server is the latest executable version, and then delete the folder that was originally stored in the local name.

2. I submit a file locally to the server. Every time I submit the file, there will be a problem. If this file is missing, the file is missing. I did not know how to submit it carefully, it was not found that there were fewer files until they were used. It was very troublesome to compare the files one by one.

Cause:

"Check in" directly when submitting the file ". The check in action only updates the file in the check out state, not considering the newly added file.

Solution:

When submitting a file, you do not directly check in the selected file in VSS. Instead, you can drag the file from the local folder to the VSS directory. In this case, VSS classifies submitted files, checks in files that exist on the server and are in the check out status, and adds files that do not exist on the server; you cannot submit a file that already exists on the server but does not check out.

When submitting files, we recommend that you check whether the latest local version is consistent with the latest version submitted to the server on the date and number.

3. I directly modified the file locally and want to submit it to VSS. When I checked out, I overwritten the locally modified file and changed it again!

Cause:

For files that have been included in the VSS version management, VSS will change the file attribute to read-only. To modify a file, check out the file first. After checking out, the file is changed to normal and can be modified. You can also change the read-only attribute of a file to the normal state in the resource manager. You can also modify the file. When you check out a file in VSS, if VSS detects that the local file is not in the read-only status, the following prompt is displayed:

In this case, if you select "lave this file ?" The version of the local file will be retained. If you select replace your local file with this version from sourcesafe, the local file version will overwrite the version of the VSS server.

Solution:

1. Try to use the check out-> modify-> check in method to ensure that the file version is not prone to errors.

2. When the above dialog box is displayed during check out, first check whether the server version or local work folder version file is the latest, and then select related options.

3. if you cannot determine whether the server version or local work folder version is the latest, You can first modify the name of the local work folder, put the checked out file and the local original file in a different directory before comparison, to determine which is the latest, modify and then submit.

4. Because there are too many file changes, I am too lazy to check out. I will delete the files on the server directly and add them again. The results showed that some files on the server still use the old version I deleted, and did not submit the new version on my local machine to the server.

Cause:

In consideration of security issues, the Administrator restricts the permanent deletion permission for most users. Most users with the delete permission can only perform virtual deletion. The deleted files are still stored in the database and can be recovered. When you submit a file, if the system still contains files of the same name in the database, the following prompt is displayed:

 

If yes is selected, the deleted files are retained. If no is selected, the files of the new local version are submitted to the server to overwrite the deleted version.

Solution:

1. For files of the same name that are still useful, we recommend that you use check out-> check in to modify the file. We do not recommend using Delete-> Add.

2. When you find the above prompt when submitting a file, first determine whether you need to submit a deleted file or a new local file, and then select Yes or No.