Legacy source control
August 21, 2019

Legacy source control

Anonymous | TrustRadius Reviewer
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.
  • 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.
  • 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.
The current status of Visual SourceSafe is not usable. There are many things that are just so out of the date that it should be retired and not looked at any longer. If you have an existing application that is stored in it, I'd consider migrating it to a modern tool.
There is no longer support for Visual SourceSafe as I believe it's been retired. There are, however, users that still use the tool and they do help if there are questions or complaints.
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.
I would not recommend Visual SourceSafe to anyone out there as there are so many better, more modern solutions that do what it does and much more. Visual SourceSafe should be retired in most cases.