Recently, the company has to introduce VSS in my promotion to manage the source code. I think the company is too small in the company, especially in the development process, which is less, including the unit testing the most basic things. There is no real specification, so I want to use VSS's use, the concept of promotion unit testing, even if there is such or have such difficulties in the promotion process, but such actions are beneficial to the company, it is also advantageous to individuals. The problem now is a "degree".
Looking at the VSS document yesterday, I found a big problem: VSS Database is a database of file forms, and can only control it through Folder permissions, this problem is also written in MS, See below:
============================================================================================================================================================================================================= ========================================
To protect the Visual SourceSafe (VSS) database and files for controlling and managing VSS, you need to use Windows security permissions to limit access. According to the steps introduced in this article, you can lock the database to achieve the following:
Only the members in the VSS Database Administrators group in the VSS Windows folder can perform administrator tasks, including VSS files and projects running Analyze and recovery archive. After setting VSS security, all VSS administrators and VSS users can use VSS in the previous way. Universal people who do not have access to the network sharing location where VSS is located, so they cannot access the database.
Locking databases cannot be available:
Project level security. You can use the VSS Administrator program to set permissions and assign tasks for specific VSS items or other VSS users, but all VSS users must have the same Windows folder permissions. Therefore, all VSS users, whether they can access the shared folders regardless of the project level permissions specified in the VSS Administrator program, and all VSS data can be fully controlled, except for those used to control and manage programs and databases. Do not use a shared database to store files that contain sensitive information, such as wages or legal documents. Read only VSS users. If you want to limit some VSS users, you can only read files in the VSS database, so you recommend that you do not set these people to VSS users, and you should create a shadow folder and grant these people access this folder. .
! The above part has a detailed description in VSS Help!
============================================================================================================================================================================================================= ======================================= 红 即 即 即 即 我 我 我 问题,,, 了, 了 了WWW, why do you have no attention to this problem? Is it only used by the so-called "professional ethics" to constrain? I think all things that have no system are very fragile. User with the Data folder permissions can fully access the Data folder through the "/" sharing mode, which should be a hidden disaster?
But in addition to this, VSS is still nice, hereby illustrative.
