Microsoft Visual Studio Reviews

The product integrates well with Azure Cloud, and it supports a ton of languages.

It also has a very good interface for Git source code management. Then there are a couple of add-ins or plug-ins that are out there in the marketplace that sometimes come in handy. From a developer standpoint, it does a very good job when it comes to debugging. It's a great development tool. 

The initial setup was pretty straightforward. 

The solution has good technical support.

It has a ton of options and that sometimes can become very, very overwhelming for a new person, a new developer. If something can be done around simplifying the product, for example, if there's a way, to just have enough options that are relevant for me, that could probably help.

The upgrade system is a bit complex. If they're upgrading something, then they should not force us to go to the next version. Maybe they should probably just release a fix or something that, and once we implement that fix, it gives us at least a choice that you're good for some time even if you don't want to upgrade.

A ton of time is just spent trying to keep ourselves up with the frequent releases that Microsoft rolls out. That is something that takes away from our productive time that we could have invested that time to enhance your application, and could have worked on additional features or functionalities, however, you end up spending that time just to upgrade your current solution to the next version that they roll out.

I've been using the solution for three years, however, my team members have been using it for ten to 12 years now.

In terms of the stability, the frequent upgrades that they roll out and then they force us to upgrade the solution, upgrade the tool itself, those sometimes can be a nuisance.

Most of the time, I see my team members end up spending a lot of time just upgrading the application to the next .NET framework. Or sometimes even the Microsoft Visual Studio version that gets rolled out and then you just have to do that upgrade. Therefore, the frequent upgrades that happen just don't support the older ones, they just take it off support, which causes a lot of nuisance.

The project that I'm part of is a huge team for sure. We are a team of a couple hundred. 

There have been instances in the past where we have reached out to Microsoft.

Support-wise, they're doing a fair job. I don't mind that. Whenever we reach out, we do get help.

It was a pretty easy setup. For us, basically, it comes with some preconfigured settings. The license that we have is a project from our customer. It is fairly straightforward.

We had a third party help us with the initial setup. We did not do it completely by ourselves.

I'm not someone who concerns myself with the cost. That said, my understanding is the license cost is a lot. Before customers roll out a license for any developer, they make sure that it is relevant and it's required for the job. 

We use the enterprise edition of the product. We're using the latest version.

We're end-users of Visual Studio. We're also using Microsoft Teams as well.

We have a couple of applications running on-prem. The roadmap is to move as much as possible onto Azure.

I'd rate the solution eight out of ten.

We use this solution to support a number of different web development processes across different tools and languages. 

This solution can integrate with almost any functionality offered by Microsoft.

We have been using this solution for three years. 

This is a stable solution. 

The initial setup is straightforward.

The pricing for licenses could be reduced to make this solution more competitive.

I would rate this solution an eight out of ten. 

One of the most valuable features is its support. It's easy for me to get support even though I never use it. If there's a bug or a performance issue, Microsoft also provides quick updates, and this is another valuable feature of the program.

A room for improvement in Microsoft Visual Studio is its performance. Currently, some of our devices are not that capable, so performance still needs to be improved.

An additional feature I'd like to see in the next release of Microsoft Visual Studio to make it better is a more centralized education system, e.g. for Microsoft to put the tutorial for the program under Microsoft Learn.

I've been working with Microsoft Visual Studio for two years, and I'm still using it.

The stability of Microsoft Visual Studio is okay, but it could be more stable.

Microsoft Visual Studio is a scalable program. It's enough for me, and I'm utilizing it a lot, and that's one of the most important things for me.

I'm using my company's equipment, so Microsoft Visual Studio is already set up on it. The program's easy to set up.

I'm using the latest version of Microsoft Visual Studio, e.g. the 2022 version if I remember correctly. It depends on what my company is using.

The most valuable thing about Microsoft Visual Studio is that it's already deployed in my company and used by my company, so I can just use it. That's the reason I'm using the program.

I haven't contacted technical support for Microsoft Visual Studio.

I'm giving Microsoft Visual Studio a rating of eight out of ten.

We use the solution to develop applications. 

Microsoft Visual Studio needs to improve integration. 

I have been using the product for five years. 

I rate Microsoft Visual Studio's stability a nine out of ten. 

The tool's deployment is straightforward. It takes less than an hour to complete. 

I can install the solution by myself. 

Microsoft Visual Studio is a free product. 

I rate Microsoft Visual Studio a nine out of ten. 

I am using Microsoft Visual Studio for developing SQL Server applications.

Using Microsoft Visual Studio has heightened the quality of the work that I do since it is checking everything.

The most valuable feature of Microsoft Visual Studio is its integration with Azure DevOps.

The migration could improve in Microsoft Visual Studio. When I upgraded from 2017 and up to 2022 it was not smooth. There was a lot of manual hand-picking.  Microsoft should put a higher budget for the database developers' section in Visual Studio.

In a future release, it would be a benefit to include an option so I can share the library of methods between different projects in SQL Server easier.

I have been using Microsoft Visual Studio for approximately five years.

Microsoft Visual Studio is a highly stable solution.

We have four or five people using Microsoft Visual Studio in our organization. We are a small startup company.

I have not used the support from Microsoft Visual Studio.

I previously used SQL Server Management Studio which is very popular for development. However, I wanted to source code handling as well, and this is why I moved to Microsoft Visual Studio.

The initial setup of Microsoft Visual Studio was straightforward. However, the difficulty depends on how much of the solution is going to be used. The installation is typically done in smaller steps at the beginning which makes it easy.

The time it took for the deployment was approximately one day.

We did the deployment of the solution in-house but we had a consultant with the GitHub integration.

The solution is expensive.

I rate the price of Microsoft Visual Studio a two out of five.

I am the only person that is needed for maintaining the solution.

My advice to others is to do small steps at the beginning to make it simple. This solution is very large and is best to do it in small steps.

I rate Microsoft Visual Studio an eight out of ten.

I use Visual Studio to build software for the Microsoft platform.

Visual Studio provides integration with GitHub, and the 2022 version makes it easy to move from one branch to another via the GUI when working on a solution. It also provides a view of how the branches are organized with the code inside the repository. 

Visual Studio's best feature is debugging, which isn't available with any other Microsoft development tool.

There's not much help to deal with issues on Microsoft's official websites.

I've been using Visual Studio since 2005.

Visual Studio is stable 95% of the time, except for an error when refreshing DLLs that requires a restart.

Visual Studio is the best tool available for working on the Microsoft platform, with features that aren't available on any other development tool. I would rate Visual Studio nine out of ten.

We use this solution for developing enterprise projects.

It is a beneficial tool because we can write programming code, write our test cases and automate tests in Visual Studio.NET. Additionally, after we develop projects, we can automate and test. It also provides an integrated development environment where we can design our page and program it. It works well both on the front and back end.

The solution could be improved by including an axle intelligence
for tech suggestions and suggesting the dependencies between API. When we use some APIs, we have to add the dependency ourselves in Microsoft Visual Studio. However, with axle intelligence, when an API is added to a project, it can find the dependency of the API and add it automatically.

We have been using this solution for about 17 years now and we are currently using the 2019 version.

The solution is very stable. It works very well once it is open and has never crashed.

The solution is scalable, and scalability depends on what we use the tool for. It has various tools we can use in whatever way we choose. Currently, six people are using this product in our company.

We have had a very good experience with customer service and support.
Whenever we post an issue, someone in the support team reaches out to us within 24 hours. Therefore, I would rate the support team a ten out of ten.

Positive

We used Borland IDE before switching to this solution. Borland C++ builder was a good product then, but we switched to this solution because we think Microsoft Visual Studio is currently the best IDE.

The initial setup is straightforward. It just needs to be downloaded and installed from Microsoft.

We implemented this solution on our own. We work with Microsoft Visual Studio on our PCs, which is installed on every PC. For each project, we have a manager and a group of about five to 60 staff members comprising engineers, administrators and managers. We extend our team and employ new people whenever we get a new project.

Unfortunately, we cannot comment on ROI because we are using the community edition.

Unfortunately, because our country is under hefty sanctions, we could not buy this product so we use the community edition, which is a free version. However, we believe the cost of licensing for this product is logical.

I rate this product a ten out of ten. This product is a very good choice for people searching for an Integrated IDE. Microsoft IDE is very integrated and does not require other tools except Microsoft Visual Studio.NET. However, the product could be improved by including axle intelligence.

It is great for integration with Excel. For example, with Microsoft Access, you can make fast elementary analyses for the business. It is very easy to use.

Microsoft Visual Studio is a powerful product that we can use for visualization. We currently use it for simple business tasks and financial graphics.

The scalability could be improved.

We have been using this solution for more than ten years, and it is deployed on cloud.

The stability depends on the solution that you need. If you use a lot of data, it's not stable, but if you use it for business tasks, it's stable because they are simple tasks.

It is not scalable, and it could be better. About 200 people use Microsoft Visual Studio in my company.

I rate this solution a four out of ten. I would recommend this solution depending on the business case. It is a very simple and nice tool for simple tasks, but I would not recommend it for complex tasks.

I can't speak to performance because it's a cloud solution, and it depends on the cloud. When you are using real-time data, you need the results immediately, so if the cloud is not fast enough, it's an issue. Results aren't provided in real-time, but if it is on-premises, this can be avoided. But if it is on-premises, you must give up some features. Therefore, it is challenging to determine performance.