Filter Ratings and Reviews
Filter 8 vetted Visual SourceSafe (Discontinued) reviews and ratings
Reviews (1-4 of 4)
Companies can't remove reviews or game the system. Here's why.
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.
- 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
- 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
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.
January 28, 2019
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.
In my organization, Visual Source Safe is mainly used to correctly manage the versioning of the various development files in Visual Studio. Since I use this product I can always have the correct versioning of the files, avoiding the loss of the code and analyzing the changes made by checking the previous versions.
- avoid losing code
- versioning of previous projects
- saving versions on db
- sometimes there are problems with check-in and checkout if done simultaneously
- the user interface is not really nice
- only source control
Visual SourceSafe (Discontinued) Scorecard Summary
What is Visual SourceSafe (Discontinued)?
Visual SourceSafe is a discontinued source control software offering, from Microsoft.
Categories: Software Configuration Management
Visual SourceSafe (Discontinued) Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |
Frequently Asked Questions
What is Visual SourceSafe (Discontinued)?
Visual SourceSafe is a discontinued source control software offering, from Microsoft.
What are Visual SourceSafe (Discontinued)'s top competitors?
Azure DevOps Services (formerly VSTS), IBM Rational ClearCase, and Perforce Helix Core are common alternatives for Visual SourceSafe (Discontinued).
Who uses Visual SourceSafe (Discontinued)?
The most common users of Visual SourceSafe (Discontinued) are from Enterprises and the Consumer Goods industry.