Sourcetree vs. Microsoft Visual SourceSafe (Discontinued)

I prefer to work visually and use the tool for merge and rebase operations. It helps when managing a large number of repos.

Incentivized

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.

Incentivized

• Allows to manage GIT repositories in an intuitive and simple user interface
• Visually represents complicated workflows and branching
• Integrates with most well known GIT repository managing services

Incentivized

• avoid losing code
• versioning of previous projects
• saving versions on db

Incentivized

• Refreshing of the interface after a commit or merge
• All elements being consistent with the repo status
• Select all button on Trach status on different branches

Incentivized

• 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 help new users onboard quickly and then use Sourcetree to handle their day-to-day SCM needs for managing CIs (Configuration Items). We can visually show management the branching and commit history to show the flow and pace of development.

Incentivized

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.

Incentivized

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.

I tried GitHub Desktop for a couple of days, but it is just not visual enough for me. It has no graph display for branches. Too much clicking is required to get info that the Sourcetree UI shows by default. Sourcetree gives you that "Big Picture" dashboard. GitHub Desktop seems unfinished to me due to its lack of this overview screen.

Incentivized

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

• In my experience, using Sourcetree actually slows down development if you're the average developer needing to do simple git actions. Getting set up is fast, but the learning curve to use the tool is just too steep if you're just looking to push, pull, commit, branch etc.
• Sourcetree is not implemented by default at our company, but is recommended as we primarily use Atlassian products. However the lack of integration with other Atlassian products means that this git GUI doesn't give any more or less ROI for your Atlassian ecosystem compared to another git GUI tool.
• For auditing and exploring history Sourcetree can be very helpful. Having all of this information in one place with a plethora of actions and tools at your disposal means you can audit repos much quicker than any other git GUI or online repo explorer.

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