Visual Studio Team System Reviews

Visual Studio Team System is kind of ubiquitous in programming because it's also what a lot of systems use for their source control. It is generally used for source control and deployment, and I have a couple of clients that use it as their ticketing system. In this capacity, it is used for setting up features to be developed in running through their development processes.

This product is easy to use compared to Git, which is the alternative source control system that Microsoft is trying to push these days. Git is very difficult to use properly and it is not as feature-friendly as Team System used to be.

I have seen customizations with Team System that allowed it to integrate into other ticketing systems like Jira, which would be a really nice feature to see.

I have been using Visual Studio Team System for approximately 10 years.

I am not familiar with any issues with respect to stability, and I have never seen Team System crash.

I have never had any problems with scaling. My clients generally work on projects that have anywhere between one person and 80 people working on them.

I have never spoken with technical support.

I did use alternatives, but it was going back to 2005 or 2006 and I don't remember what it was that we used back then. These days, it is so ubiquitous for Visual Studio development that I would not even think about it.

The initial setup is pretty straightforward. If it's in-house then you just deploy it to a server. I think that it comes with its own SQL database, as well. Then, you just link Visual Studio to the implementation and start adding files.

The installation is seamless as to what I usually do.

We have an in-house team for deployment and maintenance.

The features are fine for what it is. It works very well. It's designed for a specific niche, which is a very big niche. In summary, this is a good product that is straightforward, easy to use, and manages well.

It's a fine product.

I would rate this solution a nine out of ten.

I used this solution for software development, writing and debugging code.

What I like most is that it is a very comprehensive product.

IntelliSense and CodeLens are helpful because they help you (auto)complete your code, can show you details about methods, such as how many times it is called from other places within the code and where.

Debugging functionalities are useful too.

I also like the structure of how it creates solutions and programs. 

Visual Studio is quite fast and responsive compared to some other programs that I have used.

I would like to see the inclusion of more programming languages, especially better support for Java.

I have been using the 2015 edition for some four years. I started using the 2017 version more recently, perhaps four or five months ago.

I did have some issues with the 2015 version where on very few occasions it froze or just crashed. With the 2017 version, I have never had this problem. I have to say that with the 2017 version, the stability has improved.

We have perhaps 50 to 200 users in our company. We are spread over different locations and we have about 50 users here, whereas we have up to 200 globally.

I have never had the opportunity to speak with Microsoft directly because our company is supported by our internal group.

The 2017 version is similar to 2015, they have added a few things. One difference is the setup experience, although it is not a groundbreaking change. I know that they have released a new version, 2019, that allows for sharing of what you see also remotely. You can work on code with your colleague who is developing somewhere else, remotely.

When it comes to this solution, I am not really missing anything I needed from an IDE.

I would rate this solution an eight out of ten.

We use the Visual Studio Team System as an IDE for our CRM development. 

Visual Studio Team System is the most powerful IDE available in the market. 

The tool's subscriptions are expensive for medium and small businesses. It works fine on Windows. However, it is not stable on other platforms. 

I have been working with the system for 15 years. 

I rate the product's stability an eight out of ten. 

My company has five users for the product. 

Visual Studio Team System's tech support is responsive. 

Visual Studio Team System's deployment is straightforward and completed in a few hours. You need to select the options that you want to configure. 

Visual Studio Team System can be deployed in-house. 

The tool's licensing costs are yearly. 

I rate the product a nine out of ten. You need to be careful about the pricing. The solution can be expensive if you get an enterprise subscription. 

Our company has ten developers who use the solution's community edition on a daily basis for business process automations. 

The solution has a good framework that is user friendly and scalable. 

Accessibility switches available on the desktop should also be available on mobile devices for coding or developing on the go. 

Technical support is a bit lagging so could be improved. 

I have been using the solution for two years. 

The solution is stable. 

The solution is scalable. 

The community edition includes a forum that offers sufficient, detailed documentation. 

Documentation for the enterprise edition could be more detailed and recent so that it includes upcoming plugins and integrations. 

The setup is straightforward and I rate it a ten out of ten. 

There is no fee for the solution's community version. 

We have not explored other options because our clients prefer the solution. 

Before using the solution, it is good to have prior knowledge about how it works, how it can scale, and how it integrates with peer tools. 

There may be integrations which are not feasible in the solution's community version, so it is good to do your homework. 

I rate the solution a ten out of ten. 

The solution helps the project teams to take care of all aspects of the processes for software development.

All is fine with the solution. It is scalable, stable and has allowed us to upgrade our frameworks.

It would be nice to see some of the authentications compacted to the solution which are done with Nudi.

Support response time could stand improvement.

The price could be better. 

We have been using Visual Studio Team System for the last five years.

The solution is stable. 

The solution is scalable. 

Response time could be faster. 

We did not use other solutions prior to the current one. 

Installation is easy. 

While I do not recall its exact duration, this should be around four hours. 

Installation can be done with the help of the technical team.

The size of the team should be the same as that which we used, three to four people, consisting of managers. We have one IT manager. 

The solution could be more cost-effective. 

There is an annual licensing fee. 

If price is not a consideration, then my recommendation to others is that they go with the solution. 

The solution is cloud-based.

I rate Visual Studio Team System as a seven or eight out of ten. 

Our primary use case of this solution is to search for smugglers and for people who have open files. So we integrate everything with GDPR and then we distribute this in most parts of Europe. We have some interests in the United States too.

What I like about this solution is that it is one big framework, which everybody knows, so one can quite easily start-up new developers using it. 

We are looking forward to the new Blazer system that is coming out soon. It is currently in beta on the service side, so we are looking forward to the new version that will be on the client side too. I also would like to see an improvement in the technical support.

I have been using Visual Studio Team System for more than ten years now.

The solution is pretty stable.

The solution is very scalable. We integrate this in SQL and we can do this vertically as well as horizontally; in both directions. We have 15 users that are using the regional pseudo team system within our company, and they are all developers.

We pay additional fees for support, and it is doable. It is not the best support, but it is definitely acceptable. That is perhaps something that needs to be improved. 

We did the installation and setup ourselves and it was really straightforward.

My advice to others would be to go all the way with this solution. Don't try to find a cheaper solution. On a scale from one to ten, I rate Visual Studio Team System an eight and I'm looking forward to the new Blazers system.