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.

Microsoft Visual Studio is used for development, including recent work with AI applications across many different areas of the organization.

The language is easy to use for linking with other databases and software. As a Microsoft product, it provides native integration, making it straightforward to communicate with Azure or any database within Azure through built-in integration capabilities.

The version control feature helped us easily retrieve previous versions and track logs to see where changes occurred and when they happened.

The ability to use multiple coding languages in one place is valuable, providing a comprehensive environment for everything.

AI integration is something that every company is trying to incorporate. While Microsoft Visual Studio is working very well currently, there is still room to improve the AI functionality.

More than 10 years.

Microsoft Visual Studio is very stable.

Scalability rates about seven out of ten.

Microsoft sometimes has outsourced people with less knowledge on their support team. When we open a ticket, it often needs to be escalated to the next level to reach an expert, rather than being resolved at the first level. This sometimes wastes our time, but eventually they fix the issue for us.

The installation process is very easy and straightforward.

Microsoft Visual Studio provides a positive return on investment.

The setup cost rates about eight out of ten.

Different divisions in the organization may use AWS, though this is not something I am aware of directly. The organization primarily bases its operations on Azure. My overall rating for Microsoft Visual Studio is ten out of ten.

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.

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.

We use it for comprehensive support in software development, encompassing tasks such as code writing, unit testing, and deployment to both cloud and on-premises services.

It proved versatile for diverse purposes, serving as a valuable tool for developing solutions across web, desktop, and mobile platforms. It facilitated not only coding activities but also aided in managing repositories and deploying applications to various environments, whether they be cloud-based or on-premises infrastructure.

Within Visual Support, there are three versions available, each housed in distinct containers. I'm focusing on the Enterprise version due to its customizable nature. This version boasts additional features, such as a pricing application for enhanced functionality and comprehensive unit testing coverage. The testing capabilities extend to diverse features, providing a thorough examination of different aspects. Notably, the Enterprise version facilitates seamless integration with Microsoft products, leveraging the ease of connectivity within the Microsoft ecosystem. Moreover, it supports integration with open-source products, including Python, allowing for a flexible and inclusive approach to development.

When using Visual Support for web development, challenges arise when specific components require hardware configurations beyond the application's scope. Efforts are directed at enhancing the IDE and introducing features for seamless collaboration, extending to Azure with the Explore version. This version incorporates "live share," enabling real-time code collaboration among team members. Despite its advantages, challenges in diverse cloud environments may prompt the uninstallation of the application or entire development environment for resolution.

I have been working with it for approximately thirteen years.

The stability is noteworthy because Visual Studio offers both a release and a preview version. The release version is reliable, free of issues, and suitable for general use. However, for those seeking additional features and improvements, the preview version is available. This version allows users to test new features directly and report any issues to the community for resolution. While encountering some issues in the preview version, they are typically addressed promptly through community feedback, resulting in a stable and refined release version shortly thereafter. I would rate it eight out of ten.

High scalability makes it a strong recommendation, especially for enterprise-level development, given its robust capabilities as an integrated development environment. I would rate it ten out of ten.

I've interacted with Microsoft support, but the community support for Visual Studio testing has been particularly outstanding. Unlike conventional support, the community channels provide an open and collaborative environment, similar to open-source platforms. This allows users to easily report issues, open discussions, and communicate effectively, making it a gateway to a more responsive and interactive support experience.

Having used various products at different companies, I must highlight that Microsoft's development technology, particularly in the realm of databases, has proven to be more intuitive and superior. It demonstrated a higher level of user-friendliness and efficiency.

The initial setup is straightforward. Simply download the controller and proceed with the installation, selecting the desired options for a new environment and clicking through the prompts. I would rate it nine out of ten.

Setting it up in the initial stages used to be a time-consuming process, often taking more than an hour. This was primarily due to the need to download setup data, often distributed on CDs or DVDs, and then proceed with the installation. Additionally, a decade ago, machines were not as swift, further extending the setup time. However, in recent years, there's been a more efficient option. Users now have two options: an online installation and an offline installation. For the online version, users simply download it and direct it to the storage directory on their machines.

The pricing varies depending on the version, and with three options available (Community, Professional, and Enterprise), you can choose based on your needs. While the enterprise version can be relatively expensive due to its comprehensive features, I find the license I currently possess to be reasonable, considering it includes the full suite without additional activations or charges.

Overall, I would rat it ten out of ten.

We use Visual Studio for website development and related tasks. It's been quite helpful for us.

From a professional perspective, I've been using Visual Studio since childhood, so I find it very useful. The code analysis tool is particularly valuable as it eliminates the need for manual code reviews.

Many essential features are built-in, making it a great tool. Additionally, it allows for easy integration with other tools like MS Teams, which enhances its usefulness.

Sometimes, the deprecation of packages can be a challenge. Although Visual Studio provides suggestions when we compile and encounter deprecated packages, it can still be confusing. Even after multiple attempts, we may struggle to fix these deprecated packages and related issues. So, it is one of the areas of improvement in Visual Studio.

I have been working on a website that I inherited from a client, and when I tried to run it on my system, I discovered that some of the packages were either depreciated or no longer in use. It would be helpful if Visual Studio could suggest and handle such unused packages in a more user-friendly manner.

I am suggesting this as an area of improvement because recently I was working on a bigger client project. The project was functioning correctly on my system but not on another system. Later, I found that some packages were depreciated, which might have caused the issue. However, we couldn't determine the exact reason for the difference in behavior because we used the same ZIP file and the same Visual Studio version. Then, when the person tried to run the same code on her system, it didn't work. It seemed to be related to the deprecated packages. Ultimately, the solution we eventually found was to set up a new system for her, reinstalling Microsoft Visual Studio and related components.

Another area that could greatly benefit from Microsoft within Visual Studio is unit testing. It's a pain point for every software developer. If Microsoft can provide better tools or features related to unit testing, it would be really helpful. Especially when working on complex projects, writing comprehensive test cases can be time-consuming. However, clients often cannot afford to pay for that additional time in the competitive market.

So in future releases, having some automation capabilities or built-in support for generating test cases would be great. Although we can integrate third-party automation testing tools, they are often paid solutions. For example, I've noticed the presence of plugins like ChatGPT in Visual Studio Code, but I'm not fully aware of their capabilities. Therefore, if Visual Studio could offer some level of automation for test cases, it would be a valuable addition.

I have been using Microsoft Visual Studio for over 15 years.

I would rate the stability of Visual Studio a ten out of ten.

Microsoft has gained a lot of confidence in the market, so I would rate the scalability of Visual Studio around eight out of ten.

Based on my recent experience, sometimes, we faced difficulties with the same set of codes. Therefore, considering the recent incident, I leaned toward an eight and not a ten for scalability.

In my company, around 20 people are using this solution.

The initial setup is very simple. Microsoft has made it very easy to set up.

Price-wise, it is good. We are using the paid versions, and the price is reasonable. For our company, it's a genuine price.

I have only worked with Visual Studio.

Overall, I rate it a ten. It's very user-friendly and feature-rich.

However, there's always room for improvement in the product. Features like automation test cases to meet market requirements would be beneficial.