VSS for enterprise
Overall Satisfaction with Visual SourceSafe
Visual SourceSafe (VSS) is still used across the organization. We are in the process of trying to migrate off this platform as well as off of Microsoft Team Foundation Server. We are migrating towards Azure DevOps. Visual SourceSafe has reached its end of life and we have experienced many issues.
Pros
- At this point in its lifecycle there are not many things VSS does well
- Its main strength would be its ability to be self contained on a local drive
- It is a basic Code repository
Cons
- VSS is prone to corruption causing the DB to have to be rebuilt
- It does not perform well if you have a lot of code in it it will be very slow
- No searching basic tree structure
- There were many benefits years ago when this product first came out
- Now there is only risk for an enterprise
- The corrupted DB issues have cost hundreds of man hours to correct
We selected Microsoft Visual SourceSafe because at the time none of these other products were out there. Now we are trying to migrate all our legacy code from Visual SourceSafe to Azure DevOps. Unfortunately we don't have a value proposition for some of the older products so we are forced to leave them in place.
Comments
Please log in to join the conversation