Legacy source control
August 21, 2019
Legacy source control

Score 1 out of 10
Vetted Review
Verified User
Overall Satisfaction with Visual SourceSafe
Visual SourceSafe was a great tool for its time, but it has fallen to the wayside in recent years. Our organization still has code that is still stored in it from a legacy perspective, so we still have to use it from time to time. We hope every day that it does not corrupt when we open it up.
Pros
- It has outlived most of the competition out there.
- It's good at maintaining exclusive locks.
- It's good at being kept on a network share.
Cons
- Becoming corrupt and having to be rebuild from a previous version.
- It can be extremely slow to check in & out of.
- Lost support several years ago from Microsoft.
- We've lost a lot of hours rebuilding our solution based on lost work/corrupted files.
- Only having a single person work on a single file has killed performance
- No CI/CI capabilities and had to find other ways to do the process.
- Azure DevOps (formerly VSTS)
Azure DevOps is a much better, more modern tool that Visual SourceSafe and everyone should be moving to it. Most if not all the integration that is there can be done or emulated in it.
Comments
Please log in to join the conversation