Microsoft Visual Studio Reviews

I use Microsoft Visual Studio to automate some processes within the establishment.

I love the integration with Microsoft Visual Studio and GitHub, the NuGet Package Manager, and its integration with Python. The database SQL Server integration is valuable. I can add a SharePoint connection and link it to SharePoint on the web for internet applications within the organization.

The Azure integration with Microsoft Visual Studio is perfect and wonderful. From Microsoft Visual Studio, I can easily deploy cloud applications directly to the IDE without connecting to the Azure portal. I can build and deploy cloud applications directly from the IDE without switching to the Azure portal.

Microsoft Visual Studio has done enough from my perspective. I am not a core developer, so I just use the basic tools that I need for basic things. A core developer would easily see additional things that could be done. I am satisfied with what is currently available.

I am using the community version of Microsoft Visual Studio, so I would not be in the right position to tell whether it is very expensive. However, I feel the pricing can be lower for small to medium enterprises to afford it. Many smaller organizations still leverage the community version. The cost can be made more affordable for these businesses.

I have been using Microsoft Visual Studio for more than ten years.

The initial setup of Microsoft Visual Studio is user-friendly, simple, and precise. The setup was fast as long as there is good internet bandwidth.

I did the installation of Microsoft Visual Studio from start to finish.

I did not evaluate other options or vendors for Microsoft Visual Studio. I have a question about whether there is room for a one-off license for Microsoft Visual Studio. Instead of subscribing yearly, is there a buyout option where I can subscribe to this once and it remains my code for life? Could there be a one-off option off the shelf instead of yearly subscriptions? If the license becomes yours permanently and can be applied to two, three, or four systems, that would be beneficial. I already know how to use Microsoft Visual Studio, so I did not explore additional options. I have used it for more than ten years. I give this product a rating of nine.

Microsoft Visual Studio is used for development. Recently, after moving into a management role, I open the projects and conduct the code review process. Different use cases have emerged over the years.

The recent project was specifically for Python development. I used Python to write a fire translator that uses Python code. This is for a specific API like the gateway, a translator that translates the information coming into the system, which is JSON, and converts that into fire and sends it back.

I have used Microsoft Visual Studio for PHP, C#, C++, and many different languages over the years. Recently, it has been used for AWS services to develop the functions.

I appreciate the debugging capability of Microsoft Visual Studio the most.

The tracing of the debugging is what I value. I can use any editor to write the code, but Microsoft Visual Studio has strong capability.

Microsoft Visual Studio has good integration with the plugins I want to use, the different types of plugins available for different languages and even JSON.

Microsoft Visual Studio has improved significantly. Before, people used to use Notepad and other basic editors. Using the studio gave them the capability to properly debug and find issues. Additionally, it provides good code organization and indentation, as well as color coding for comments. It is very useful, as it gives function descriptions and class descriptions. It is very easy for someone who is not writing the code to understand it when they look at it, as it is very descriptive with proper commenting.

I cannot give exact statistics on time saved, but I can provide statistics on quality improvement. The coding standard has been enforced. It has tremendously improved with Microsoft Visual Studio. I would say anywhere between 20 to 50% improvement, depending on which team we are discussing.

I wish Microsoft Visual Studio was not bulkier. With certain .NET frameworks, it is used and it is somewhat bulky. That is the only thing that I can identify. Probably sometimes the load time is more significant compared to other lightweight editors.

I have been using Microsoft Visual Studio for about close to 15 plus years now for different aspects of it.

There are occasional crashes and stack overflow issues with Microsoft Visual Studio, but other than that, in most cases it works.

Microsoft Visual Studio handles growing projects or teams well for my organization.

People have used different editors like Notepad and text editors before Microsoft Visual Studio. To ensure that everybody is on the right track, we decided to go with Microsoft Visual Studio and also the capability that it provides.

We have used different editors like Eclipse and other options before choosing Microsoft Visual Studio.

From the development point of view, I have seen a return on investment with Microsoft Visual Studio, but not from the organization point of view. In the sense, if the quality has improved, then definitely the productivity has improved. In that way, I can see a return, but not otherwise.

Microsoft Visual Studio's editor is doing a good job from a UI perspective.

It is convenient to use Microsoft Visual Studio. The UI is great. It helps to develop and to properly indent code.

I am not directly involved in the pricing of Microsoft Visual Studio because that is a separate organization that takes care of it, so I cannot answer that question.

I would recommend going ahead with Microsoft Visual Studio. It is a great product. I give this review a rating of 8.

My main use case for Microsoft Visual Studio is for writing code. Since I'm a data engineer, projects I work on using Microsoft Visual Studio are related to data engineering. We have GitHub or Bitbucket or GitLab repos that we clone into a local system, and we use Microsoft Visual Studio to write code. That code can be related to any of the programming languages, and if we want to also set up the pipelines or anything, it involves a variety of multiple languages such as Python, C++, and YAML files.

We use Microsoft Visual Studio to configure a virtual environment for our Python environment, install libraries there, have an organized structure, make the code editor more user-friendly, and it provides us with features like widgets, extensions, and a tool that works like Postman.

Great features Microsoft Visual Studio offers include integrations with every sort of environment. For example, if we want to open CSV files, it has the extension for it. Additionally, it includes Python linting for great indentation and creating a great structure of the code, along with extensions for SQL files or any other thing you might think about. Microsoft Visual Studio works as a great tool for developers to write code and work together as a team.

Out of those features, the UI of Microsoft Visual Studio stands out as the most helpful for my daily workflow since its UI is much more user-friendly and makes things easy to work with.

Microsoft Visual Studio is deployed in my organization in two ways. For Lambda code, AWS provides Microsoft Visual Studio console, and we also write our code on EC2 instances where we install Microsoft Visual Studio Code. Thus, we use it in both a private cloud and local environments, including multiple use cases in the AWS console for Lambda functions and under VPC for EC2 instances, as well as in a free public environment on our local computer systems.

We use AWS as our cloud provider.

Microsoft Visual Studio has positively impacted my organization as it is the single IDE used across our organization. We currently use it to write our code, and since it's a single platform, it enables coherence and resolves environment-based issues that we face. It eliminates that issue since all of us are working on the same IDE. The configs remain the same, and things are pretty straightforward. It also provides us with a preview and a debugger, which helps in debugging our application much quicker.

Using Microsoft Visual Studio has led to measurable improvements, as it helps us identify errors easily and preemptively due to the extensions and other integrations. We don't need to search specifically for errors because it automatically detects them, improving our productivity and reducing our development time. With the integration of Copilots and AI chatbots, it has also helped in improving our overall productivity and workflow.

I think Microsoft Visual Studio is good at the moment.

When I think of additional improvements, I would like to have the ability to use Claude in my Microsoft Visual Studio account since I believe that would be a challenge at the moment. I'm not sure if it can be done, but if it was a native feature provided by Microsoft Visual Studio Code or if it was easier to do, I think that would create a much easier path to develop things faster.

I chose a rating of 9 instead of a 10 because there might be some improvements that can be made with the coming age of AI. Microsoft Visual Studio is already good. If the Claude integration is improved or if any other enhancements are made, apart from that, it's almost perfect.

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

Microsoft Visual Studio is stable.

Microsoft Visual Studio's scalability is not an issue. It is installed locally, so it doesn't present any problems.

We didn't require any customer support for Microsoft Visual Studio.

Neutral

Some organizations previously used JetBrains and PyCharm, which I found typical and boring. Microsoft Visual Studio gives me much more freedom, and it is fun to use.

My experience with pricing, setup cost, and licensing is that since we install it directly from downloads, the cost is minimal. If we have a Microsoft Visual Studio enterprise license, I'm not sure about the cost of that.

I'm not sure if I purchased Microsoft Visual Studio through the AWS Marketplace. I think I installed it directly. For the local environment and for EC2 or AWS console, I think it provides it natively.

I have seen a return on investment since using Microsoft Visual Studio helps in debugging easily and identifying syntax errors preemptively. In that way, we save time, which is a form of return on investment.

My experience with pricing, setup cost, and licensing is that since we install it directly from downloads, the cost is minimal. If we have a Microsoft Visual Studio enterprise license, I'm not sure about the cost of that.

Before choosing Microsoft Visual Studio, I evaluated a variety of options including PyCharm and Sublime Text. I found Sublime much more simple and plain, so it didn't provide many features. PyCharm had some great utilities, but it is very in-depth and I'm not used to it. Microsoft Visual Studio is much faster, easy to navigate, and helps in solving things quickly.

My advice to others looking into using Microsoft Visual Studio is that it's a good product, and they should go for it since it's the industry standard.

Microsoft Visual Studio gives me much more freedom, and it is fun to use.

Microsoft Visual Studio is stable.

I have covered all of the points about Microsoft Visual Studio, and I would rate this product a 9 out of 10.

My main use case for Microsoft Visual Studio is writing file processing code and backend APIs.

A specific example of the kind of file processing or API work I do with Microsoft Visual Studio is processing files from the client about their card transactions.

There are no other types of projects or tasks that Microsoft Visual Studio helps me with.

The best features Microsoft Visual Studio offers are the debugging and IntelliSense, which stand out to me the most.

The debugging and IntelliSense features in Microsoft Visual Studio help me in my work because the debugging lets us step through code when we're having issues and the IntelliSense helps us with basic syntax errors.

Microsoft Visual Studio has positively impacted my organization because with Live Share, we were able to collaborate on code projects.

Live Share helped our team collaborate by saving time, improving code quality, and assisting with remote work, as we were able to quickly resolve issues or build features.

I wish Microsoft Visual Studio was available on the Mac for improvement.

I just wish it worked on the Mac.

I have been using Microsoft Visual Studio for about eight years.

Microsoft Visual Studio is stable.

The scalability of Microsoft Visual Studio is fine; we just install it locally.

I have not needed to contact the customer support team for Microsoft Visual Studio.

Negative

I previously used VS Code and other IDEs before Microsoft Visual Studio, and I switched because Visual Studio just had more fleshed out features.

I wasn't involved in the pricing, setup cost, and licensing, but I'm pretty sure it was free to install.

I have seen a return on investment because Microsoft Visual Studio has saved my team time.

Before choosing Microsoft Visual Studio, I evaluated VS Code and other IDEs.

I would not add anything else about the features of Microsoft Visual Studio.

I would rate Microsoft Visual Studio a seven out of ten.

I rate it a seven because you can't use it on all platforms.

My advice to others looking into using Microsoft Visual Studio is that it's free, so try it.

My main use case for Microsoft Visual Studio is writing code, specifically infrastructure as code to build resources in cloud platforms such as AWS EC2 instances, Google IAM resources, and networks within Azure.

A specific example of a project where I used Microsoft Visual Studio for infrastructure as code is creating Google Cloud projects. The project can be defined using Terraform, and I can write those scripts within Microsoft Visual Studio and execute them from there as well, using the built-in terminal.

I have also briefly used Microsoft Visual Studio for connecting to databases because there is an add-on for PostgreSQL, which allows me to see my code in one section and then connect to a database using my code in another section. That functionality is quite useful.

Microsoft Visual Studio impacts my organization positively because it is used across the organization to write, commit code, and execute code. It works as an environment for many engineers. The fact that everyone is on the same platform is very useful because it is very easy to teach colleagues how to use it.

Some of the best features Microsoft Visual Studio offers include a user-friendly UI element where you can download different themes, which is great because it allows you to read the code much clearer. There are many add-ons within Microsoft Visual Studio because I believe it is probably the most popular IDE out there, which leads to many useful add-ons. Additionally, I appreciate the fact that the terminal is built in, so you can execute your code in the same window rather than having to open a separate terminal and execute from that.

The built-in terminal is what I find myself relying on the most day-to-day because I use that every time I use Microsoft Visual Studio. It allows me to commit my code very quickly and also run shell scripts via the terminal that I might be editing as well. I use it heavily; I know some people do not use it as much and prefer a separate terminal, but I find that I am able to work much quicker and more efficiently using the built-in terminal.

The feature that makes Microsoft Visual Studio really stand out compared to other IDEs is the number of add-ons that it has, because with it being probably the most popular IDE, it has a lot of support. There really is not any other IDE you would want to use rather than Microsoft Visual Studio. The fact that it is free as well is pretty impressive.

I think Microsoft Visual Studio is a very good tool and I do not have many improvements to suggest. The only thing I can think of is that I quite regularly get notifications that interrupt my workflow, telling me that Microsoft Visual Studio could be updated. I would appreciate a feature where it can auto-update during times when I am not working so that it can update in the background because sometimes I am writing a script mid-concentration, or maybe I am using the built-in terminal and I am about to execute a command, and then a pop-up appears, derailing my train of thought.

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

Microsoft Visual Studio is stable.

Microsoft Visual Studio is highly scalable; you can have thousands of engineers using it at the same time and because it is deployed locally on their machine, there would not be any scalability issues. The scalability is immense.

I have never had to reach out for customer support, but because it falls under Microsoft, I presume organizations with a Microsoft support agreement would be able to reach out. I have interacted with Microsoft support in the past when using Azure, and they have always been very helpful, so I would imagine the support would be great.

I have only ever used Microsoft Visual Studio in terms of IDEs in an enterprise environment. The only other IDE I have used is Replit, but that is for my own development. It is a very lightweight, web-based IDE, but there is no need to use a different IDE rather than Microsoft Visual Studio. It has everything you would want in an editor, which is why it is so prevalent in the industry.

From a cost savings perspective, I have definitely noticed improvements because there are some IDEs where you have to pay for a subscription to use it. I understand that the cost can really accumulate, especially if you have a huge engineering team using it. Whereas Microsoft Visual Studio, being free, completely eliminates the costs associated with using a different IDE. Teams can very easily see cost savings of 100 percent because you are going from something which did cost before to something which is free.

My experience with pricing, setup costs, and licensing for Microsoft Visual Studio is that the pricing is free, which is perfect.

Before choosing Microsoft Visual Studio, I did not evaluate other options because it was always the option due to it being free and because it is the market leader.

I would advise others looking into using Microsoft Visual Studio to use it because it is free, it is the market leader, and it has a ton of add-ons. There is really no reason not to use it. I gave this product a rating of ten out of ten.

My main use case for Microsoft Visual Studio is as an IDE.

I use Microsoft Visual Studio for any of my .NET work.

I use Microsoft Visual Studio for debugging, testing, and collaborating with teammates.

The best features Microsoft Visual Studio offers are the debugging tools, which are quite effective.

What I appreciate about the debugging tools in Microsoft Visual Studio is the UI, which makes it easy to use.

Microsoft Visual Studio has positively impacted my organization by helping with productivity through collaboration. It has helped with productivity because we use it to collaborate.

Microsoft Visual Studio has helped with collaboration by using mob.sh for team projects.

Microsoft Visual Studio is a solid IDE overall. There could be some additional customization on the themes for the visual aspect to make it easier to read the code, though plugins are available for that.

I don't have other needed improvements for Microsoft Visual Studio beyond themes or plugins.

I have been using Microsoft Visual Studio for about four years.

Microsoft Visual Studio is stable.

The scalability of Microsoft Visual Studio has worked well so far. I haven't run into any significant issues.

I haven't had to reach out to customer support for Microsoft Visual Studio.

It's project to project with Microsoft Visual Studio, but sometimes we use JetBrains and sometimes we use Visual Studio, depending on the project.

I don't remember my experience with pricing, setup cost, and licensing because the company handled most of that for me.

Microsoft Visual Studio has likely saved some time and money because we can use it for many plugins, though I don't know the specifics.

My advice to others looking into using Microsoft Visual Studio is that if you're running a .NET project, it's the best IDE we've found so far, and it's a solid, stable product. I would rate this review a 7.

My main use case for Microsoft Visual Studio is coding and looking at the logs. Whenever I have a log file which is very large, I open it in Microsoft Visual Studio because it can handle big files and then make it easy to search and scroll.

The best features Microsoft Visual Studio offers include being smooth in coding, allowing the opening of large projects and large files. Microsoft Visual Studio is smooth because it can handle large projects and open large files without hanging, and it still allows large search functionality.

Microsoft Visual Studio is one of the main tools that has impacted my organization positively. We can create custom plugins in Microsoft Visual Studio which are specific to our company and our organization, and use them, which is quite useful, and this has helped our team and projects.

Allowing coding for more formats in Microsoft Visual Studio could be an improvement. It should allow more formats when it comes to APLR coding and what I would like to see improved or added in this area.

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

I think Microsoft Visual Studio is stable.

Millions of users use Microsoft Visual Studio worldwide, so I think it is quite stable in terms of scalability.

I haven't interacted with customer support at all.

We have been using Microsoft Visual Studio for some time, and I did not previously use a different solution.

The IT team handles the pricing, setup cost, and licensing of Microsoft Visual Studio, so I have no idea about that.

The IT team handles the pricing, setup cost, and licensing of Microsoft Visual Studio, so I have no idea about that.

I don't have insights into a return on investment, including relevant metrics, like time saved or fewer employees needed.

The IT team handles the pricing, setup cost, and licensing of Microsoft Visual Studio, so I have no idea about that.

I don't think I evaluated other options before choosing Microsoft Visual Studio, as I was not part of the team which does that. I have no visibility into that.

On a scale of one to ten, I would rate Microsoft Visual Studio a nine overall. I give it a nine because it does not support Android. The one thing that would make it a ten for me is related to the formats I mentioned. I think others looking into using Microsoft Visual Studio should use it, as it is a good tool. I would rate this product nine out of ten.

Neutral

The main use case for Microsoft Visual Studio is module development and software development, and I do some unit test work as well.

Microsoft Visual Studio's integration with Git and Team Foundation Server is the most valuable. We can work on branches, check work out, merge work in, and resolve conflicts with it, so those are all good features in Microsoft Visual Studio.

I have used IntelliSense in Microsoft Visual Studio, and when you hover over a data type, you can see that you can get more information about it and its interface, which is a good feature.

The debugging tools in Microsoft Visual Studio are very good at helping me pinpoint issues with precision.

The Git integration in Microsoft Visual Studio is brilliant.

The main benefits Microsoft Visual Studio provides include streamlining processes, and it's fairly intuitive, where most of what I need to do can be accessed from the dropdown menus. It takes a lot of the tricky part out because you've got it all there in an integrated development environment (IDE).

Based on my experience and my colleagues' feedback, I believe a potential area of improvement for Microsoft Visual Studio could be incorporating more AI, as it makes things easier for us, and having more intelligence in the tool would be beneficial.

In terms of functionality, I am mostly satisfied with Microsoft Visual Studio, but I would suggest that it provides more help with being able to use design patterns.

I have been working with Microsoft Visual Studio for approximately 12 years.

In terms of scalability, I would rate Microsoft Visual Studio an eight.

I have had some experience with tech support from Microsoft, and I would rate them a seven, although I haven't had to really use any desk support from them.

I would rate tech support from Microsoft an eight, as I'm sure they're good, but we just haven't had to deal with them that much.

Positive

The initial setup for Microsoft Visual Studio isn't too difficult.

The stability of Microsoft Visual Studio is excellent, deserving a rating of 10.

Microsoft Visual Studio is the best tool that we've got currently, and I don't have any complaints about it. I give it a final rating of 10 out of 10.

Neutral