Visual SourceSafe - An outdated product
January 28, 2019
Visual SourceSafe - An outdated product
Score 1 out of 10
Vetted Review
Verified User
Overall Satisfaction with Visual SourceSafe
We are still using Visual SourceSafe for a few software projects that weren't yet migrated to SVN or Git. At the time when these projects were started (many years ago), VSS was pretty much the best available option on the market for versioning of our source code. It allowed us to keep it stored on a server and not on the local development system and to allow more people to work on the same project.
- The integration with Visual Studio is its best asset for developers using Visual Studio for software development.
- File versioning - creates file versions with notes.
- Ability to add tags to create a project version.
- Ease of administration.
- The system stability could be improved. Often we get file corrupted errors.
- The User Interface is not modern and not user-friendly.
- Concurrent check-outs could be added, allowing more people to work on the same file at the same time.
- Add conflict resolution, files comparison, blame file, features that any modern source control program should have.
- When we started using it, it allowed us to do source code versioning and store the code in a centralized location and not locally.
- We are using it for very few projects with few developers that still maintain those applications and do not have time to merge the source code to Git.
Git is a much more elaborated tool for file versioning than Visual SourceSafe. It has superior performance and stability, it is cross-platform, distributed, it gives you a better User Interface (if you choose to buy Bitbucket), it allows you to have big projects with big teams, it has branching, merging etc.