New guy on the VSTS block.
October 17, 2017

New guy on the VSTS block.

Clay Horste | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Microsoft Visual Studio Team System

We are moving our entire code base from on-prem TFS to Visual Studio Team System(VSTS) with GIT repositories. We are taking the opportunity to move to a complete continuous integration solution. We also feel that moving to GIT will improve code quality with the way that branches are lightweight and how code reviews are a fundamental part of the way you do things in GIT.
  • Integration with Visual Studio
  • Option to use GIT or TFS repositories.
  • Plugins galore.
  • I think the documentation lags too far behind the actual product.
  • Troubleshooting could be easier.
  • There are some glaring pieces missing or are just obscure to use. The way you publish a built website is pretty bizarre.
  • Since we are still transitioning, there hasn't been a real impact.
Our TFS was dated and in some ways was quite crude. VSTS is thoroughly modern and I don't have to worry about updating it since MS is always updating VSTS. Also, VSTS has better integration with other products such as JIRA than our older TFS would. I am sure you could integrate TFS with anything, but it was some serious work.
I think it is a great place for a Microsoft shop to move to. If you are already on a TFS based system, there are a lot of tools to move your code base to Visual Studio Team System. I think it is overkill fone-mane man band. Just use GIT and set up build agents locally if that is the case.