Microsoft Visual Studio Reviews and Ratings

Use Cases and Deployment Scope

I am using Microsoft Visual Studio for developing applications using python, I am using Microsoft Visual Studio developing desktop application using python tkinter, pyqt. And I am using it for scheduling tasks using python.

The AI assistant with GitHub copilot extention is very helpful to write the code and develop the better codes. The easy way of adding extensions helps a lot to get the work simple and quick complete to meet the deadlines. Easy way of handling database, js, c++ makes good. The connection with Git helps for version control so I can track the work status and updates.

Likelihood to Recommend

Microsoft Visual Studio is well suited for the projects with small requirements and when the project requirements are heavy then it will use most of the CPU and GPU. For the python projects it will be easy to debug and test the software easily. The advance debug tools help the testing ease.

For version control I will suggest it.

Use Cases and Deployment Scope

This is our IDE of choice for Optimizely projects. It's fast, accurate and easily handles the complex C# projects we throw at it. We use Microsoft Visual Studio for development across teams, creating custom extensions to be shared and reused across teams. The intelligent type safety system ensures our teams are accurate and can learn at the same time.

Likelihood to Recommend

The only faults are compatibility with non windows systems. With .net core being cross OS compatible, I would like Microsoft Visual Studio to be compatible with Linux. But on windows Microsoft Visual Studio is great, runs well, allows all the customisation we could need.

Use Cases and Deployment Scope

We're using Microsoft Visual Studio to develop .NET applications and maintain legacy .NET Framework web apps.

We're currently using it to develop APIs, Blazor Webassembly apps and .NET Framework Webforms applications.

The Github Copilot integration is great, because it helps writing and debugging code easier.

The git functionality is also very good; Microsoft Visual Studio is the default tool we use to resolve merge conflicts. It's very easy and intuitive to use.

Likelihood to Recommend

Well suited: anything inside the .NET ecosystem.

Inside the .NET ecosystem editing, running and debugging Blazor Webassembly apps is a great experience, even better than other editors like Jetbrains Rider.

Less appropriate:

- Other frameworks outside of Microsoft, like Angular, React, Vue, or even just regular typescript.

- CSS editing in pages, for example, when selecting a class inside some HTML Microsoft Visual Studio might not autocomplete the available classes reliably.

Use Cases and Deployment Scope

As a developer I rely heavily on Microsoft Visual Studio. It is a full featured IDE that allows me to develop, test and debug code in one location. The product is mostly stable and rarely lets me down even when working with large projects. I use other tools for working with my repositories or working writing scripts (bat, sh, etc.) as there are other tools that I prefer for these tasks. I also will use command line tools for building the project on platforms other than Windows.

Likelihood to Recommend

Microsoft Visual Studio is great for working with large projects especially when combined with cmake to generate and maintain the projects. It is very flexible to lay out the different windows (code, error, watch windows, etc) the way you want them and has all the tools you need in one place.

Use Cases and Deployment Scope

We needed a good and reliable IDE to program our multiple programs with. It needed to be easy to manage licensing, easy for developers to use, and include strong debugging tools. VS met all of those requirements for us, plus our team was already familiar with it, which made it a no-brainer to go with.

Likelihood to Recommend

It's been great for our small dev team. It's met all of our coding needs and has been easy to implement and add new users as we grow. I could see other IDEs being better for some of the languages that we don't use.

Use Cases and Deployment Scope

I am using Microsoft Visual Studio for developing websites, including backend (API development) and frontend (JavaScript &Angular). The main scope of the websites are healthcare management. I am using Microsoft Visual Studio for developing, debugging, testing, and publishing the built project to the website. I am using the IntelliSense autocompletion for faster development. I am using Microsoft Visual Studio 2019 and 20122 but I recently switched to 2026 version.

Likelihood to Recommend

For writing a Console programs or Windows Forms programs, I simply use the template to start writing the code. The I can instantly view the errors, correct them and run the program.

Use Cases and Deployment Scope

We use VS for everything from our main website to services (Windows and web), console apps, etc., to allow data exchange between multiple systems. Currently, we have several apps that automate our billing, inventory management, user management, etc. We also have a few websites written in VS. It's a great product that lets us quickly produce high-quality apps.

Likelihood to Recommend

It's great for web/windows/, and services (web and Windows), console apps, etc. You can even do your database development inside VS. The only place I can see it lacking is mobile dev, but other products out there pick up on this. A Caveat to this is MAUI; I haven't used it yet, but from what I see, it seems to be the bridge for Mobile/Web/Windows dev, all in one place.

Use Cases and Deployment Scope

Our organization develops software solutions for customers, primarily in cloud backup, recovery, and migration. We use Microsoft Visual Studio IDE to build Web, Windows, and cloud solutions in .NET. Its intuitive user interface, built-in AI features, and seamless Azure cloud integration make it easier for us to develop, debug, test, and deploy software efficiently. The product also enables our remote teams to collaborate effectively and deliver solutions in record time.

Likelihood to Recommend

I love Visual Studio as it helps me do my software development jobs with ease. It's best suited for Web, Windows, and Cloud development in .NET development.

Use Cases and Deployment Scope

Microsoft Visual Studio is at the heart of our work at Focused On Data, as we produce desktop and web solutions for clients, built on C# language.

As an IDE it is ideal for new developers allowing us to progress employees through a process of training and learning that permits them to provide valuable input in our software development projects.

Integration with GitHub is one of the major advantages, since it allows us to maintain source code in a secure repository, with the ability to have multiple developers working on the same project in a safe and coordinated way.

Likelihood to Recommend

When working with base C# code for desktop and web projects, then Microsoft Visual Studio is ideal as it provides the libraries and interfaces needed to quickly create, test and deploy solutions.

It is when slightly more complex scenarios are required that issues can arise. The built-in integration for things like PowerBI Paginated Reports and dashboards is far from ideal.

Use Cases and Deployment Scope

We use MS Visual Studio to develop applications for our internal clients. We need a powerful machine to develop the different applications, so it could be the first business problem to solve, since Microsoft Visual Studio requires significant memory and CPU to run multiple development projects on the same machine. We need to develop projects one by one, and it is not always possible to open multiple projects at once. On the other hand, when you create the project in the production environment, it doesn’t need as much capacity.

Likelihood to Recommend

When you need to develop a large project, Microsoft Visual Studio allows you to create it with a lot of possibilities. It seems you are the master and you could control all the parameters. On the other hand, MS VS sometimes requires a lot of memory and CPU to work properly, and it may not be an option for some people because machines with these components are very expensive for them.