Plastic, now part of Unity DevOps vs. Microsoft Visual SourceSafe (Discontinued)

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Plastic, now part of Unity DevOps
Score 8.2 out of 10
Enterprise companies (1,001+ employees)
Plastic was a version control system for facilitating branching, diffing and merging. It was acquired by Unity, and its features are part of Unity DevOps. The application is no longer available for sale.
$6.95
per user
Microsoft Visual SourceSafe (Discontinued)
Score 8.0 out of 10
N/A
Visual SourceSafe is a discontinued source control software offering, from Microsoft.N/A
Pricing
Plastic, now part of Unity DevOpsMicrosoft Visual SourceSafe (Discontinued)
Editions & Modules
Cloud Edition
$6.95
per user
Team Edition (on prem)
$9.95
per user
Enterprise Edition
$23.25
per user
Enterprise Edition (perpetual)
$595.00
per user
No answers on this topic
Offerings
Pricing Offerings
Plastic, now part of Unity DevOpsMicrosoft Visual SourceSafe (Discontinued)
Free Trial
YesNo
Free/Freemium Version
YesNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeOptionalNo setup fee
Additional Details* Educational institutions receive a substantial discount on Plastic SCM licensing fees * Corporate/volume pricing is available * For more information, please contact sales at sales@codicesoftware.com
More Pricing Information
Community Pulse
Plastic, now part of Unity DevOpsMicrosoft Visual SourceSafe (Discontinued)
Considered Both Products
Plastic, now part of Unity DevOps
Chose Plastic, now part of Unity DevOps
Plastic has best integration with unity - zero issues, native, straightforward. Github feels more stable but for smaller and or indie teams plastic s version control feels much more under control - you click, you feel safe. moreover, there is no need for extra tools such as …
Microsoft Visual SourceSafe (Discontinued)
Chose Microsoft Visual SourceSafe (Discontinued)
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.
Chose Microsoft Visual SourceSafe (Discontinued)
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 …
Chose Microsoft Visual SourceSafe (Discontinued)
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, …
Best Alternatives
Plastic, now part of Unity DevOpsMicrosoft Visual SourceSafe (Discontinued)
Small Businesses
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.4 out of 10
Perforce P4
Perforce P4
Score 7.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Plastic, now part of Unity DevOpsMicrosoft Visual SourceSafe (Discontinued)
Likelihood to Recommend
8.4
(0 ratings)
1.0
(0 ratings)
Usability
-
(0 ratings)
3.8
(0 ratings)
Support Rating
-
(0 ratings)
4.2
(0 ratings)
User Testimonials
Plastic, now part of Unity DevOpsMicrosoft Visual SourceSafe (Discontinued)
Likelihood to Recommend
Plastic SCM is well suited for the distributed development environment, where branching and merging can easily be handled. Its a good tool for version controlling, especially for a big team which is contributing to a big project simultaneously. Situation where Plastic SCM is not at all well suited are : If the project is smaller one and need to be handled by couple of people. So in that case setting up Plastic SCM and educating people to work on it is not at all efficient
Read full review
The only time I could recommend Microsoft Visual SourceSafe would be for a beginner who has a small amount of code that they would like to keep track of. This solution would not be recommended for an enterprise or any shop where you have multiple developers working on the same solution.
Read full review
Pros
  • Version Control
  • Organizing Workflow
  • Transparency
Read full review
  • avoid losing code
  • versioning of previous projects
  • saving versions on db
Read full review
Cons
  • Interface
  • Documentation
  • Learning curve
  • Unity integration
Read full review
  • 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.
Read full review
Usability
No answers on this topic
Overall Microsoft Visual Source Safe is very easy to use. It is a simple application that does only one thing. It has the basic windows tree structure for listing projects and solutions. There is no way to search for a particular file, project or solution. There is also no way to search the code in the files.
Read full review
Support Rating
No answers on this topic
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.
Read full review
Alternatives Considered
Plastic has best integration with unity - zero issues, native, straightforward. GitHub feels more stable but for smaller and or indie teams plastic s version control feels much more under control - you click, you feel safe. moreover, there is no need for extra tools such as gitkraken, gitlab, Sourcetree, fork, etc. it is really easy to develop games this way.
Read full review
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
Read full review
Return on Investment
  • Easy to use
  • Cheap
  • Better than git for us
  • Artists love it
Read full review
  • 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.
Read full review
ScreenShots

Plastic, now part of Unity DevOps Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of