Legacy source control
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 …
Overview
What is Visual SourceSafe (Discontinued)?
Visual SourceSafe is a discontinued source control software offering, from Microsoft.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Pricing
N/A
Unavailable
What is Visual SourceSafe (Discontinued)?
Visual SourceSafe is a discontinued source control software offering, from Microsoft.
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
4 people also want pricing
Alternatives Pricing
What is ConfigCat?
ConfigCat allows the user to launch new features and change software configuration without (re)deploying code. ConfigCat SDKs enable easy integration with any web, mobile or backend applications. The ConfigCat website enables non-developers too to switch ON/OFF application features or change…
What is Plastic SCM?
Plastic SCM is a full stack version control system that aims to make software configuration easy. It focuses on enabling dev teams get work done by facilitating branching, diffing and merging. The vendor says that for those purposes it provides cross-platform apps and GUIs with: Branch…
Product Details
- About
- Tech Details
What is Visual SourceSafe (Discontinued)?
Visual SourceSafe (Discontinued) Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(8)Attribute Ratings
Reviews
(1-4 of 4)Companies can't remove reviews or game the system. Here's why
August 21, 2019
Legacy source control
Score 1 out of 10
Vetted Review
Verified User
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.
- 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.
August 19, 2019
VSS for enterprise
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
- 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.
January 28, 2019
Visual SourceSafe - An outdated product
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.
February 08, 2018
A Good Source Control
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
- gains in avoiding loss of code
- gains in terms of hours spent on development
- gains in terms of time saved