Bower.io vs. Microsoft Visual SourceSafe (Discontinued)

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.

• 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

Incentivized

• 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.

Incentivized

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.

It's a Microsoft product so the customer support is great. The program has been around a long time so there are plenty of places on line to get assistance. Also almost any development shop you go to will have at least one developer who has used this product extensively in their career.

Incentivized

Incentivized

• 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.

Incentivized