Visual Studio Professional 2022

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.

On-premises

Other

Microsoft Visual Studio  is an IDE , or integrated development environment, which enables users to set up their own dev environment to code and build websites and then host them. Through Microsoft Visual Studio , users can host to cloud services with one button or one fly server. It's essentially an environment for coding; it's an IDE .

Microsoft Visual Studio is a robust Microsoft product. It is a very secure device and tool. It has numerous extensions and plugins available, and it's a cross-platform development tool, meaning development is possible for any other devices. It supports everything, provided you have the specific graphics for processing and a CPU with an intensive workload, a clock speed-based device.

IntelliSense in Microsoft Visual Studio can sense automatically. It can identify syntax errors and declarations if there are mistakes. It's extremely helpful during coding. With IntelliSense, issues can be rectified on the fly, either before or after compiling.

Microsoft Visual Studio's debugging tools are excellent and straightforward. Users can utilize a line-by-line debugging feature.

The built-in Git  integration for source control in Microsoft Visual Studio has a simple setup process. Users just need to provide the repo link and grant access. The integration is seamless and helpful, allowing for easy code pushing and pulling.

Some of the most impactful plugins include static code analysis tools and GitHub  Copilot. There are also JSON viewers, JSON parsers, and numerous third-party plugins available.

The performance profiling tools in Microsoft Visual Studio are effective. Once an application is ready, it can be tested with performance profiling. Users can perform performance upgrades, check function calling processes, identify redundant elements, and determine if code-level changes are needed for better processing.

Microsoft Visual Studio is performing well currently. One potential improvement would be integration with solutions such as Codespaces , where users can have their own virtual dev environment setup. A hybrid setup would be beneficial, particularly for users with low-performance PCs. A hybrid collaboration with Microsoft Visual Studio system where some processing occurs in the cloud would be more effective.

The support and community forums for Microsoft Visual Studio are strong, deserving a solid eight out of ten rating.

Positive

I have leveraged the plugin ecosystem to tailor my IDE experience. The overall rating for Microsoft Visual Studio is 8 out of 10.

Recently, I have been working with the Power Platform, which is a Microsoft product. Currently, I am exploring and doing one project as well. Power Platform is looking promising, and it provides various features. It is very easy to learn Power Platform. Power Platform may only be applicable to small size to mid-size applications, so I think it will not be applicable to enterprise level applications.

Power Platform provides workflows and database functionality. The database application is very good. When creating an entity, based on that entity, you can create views and pages automatically based on the table. That is one good feature in Power Platform. It also supports customization features, though it takes some time to understand as there are many steps for customization. If any system exposes functionality using REST API, we can get the URL and environment details such as headers. In Microsoft Visual Studio , if a system exposes services, we can consume those services by getting their proper URL/URI and header information. If they have any authentication mechanism using tokens, we can utilize those in Microsoft Visual Studio  to invoke and call the REST APIs provided by external systems.

Microsoft Visual Studio provides almost all features. When adding classes, if references to class files or namespaces are missing, improvements could be made. Sometimes when missing namespaces and calling functionalities in other classes, Microsoft Visual Studio shows errors. While clicking on the cursor shows which particular namespace is missing, when adding new namespaces, it still shows some errors. Microsoft Visual Studio should avoid these errors.

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

Issues with Microsoft Visual Studio are very rare. Sometimes crashes happen and occasionally there might be hanging issues. We close Microsoft Visual Studio and once opened again, the issue resolves automatically.

Regarding stability issues, the system makes sure it should be up and running throughout the day. In case of any downtime issues, the system will notify us about the timing so we can take appropriate actions beforehand. These informations are automatically provided by the system, so we don't need to manage this ourselves. The system helps keep the server up and running.

In the frontend, we need to download Microsoft Visual Studio, which is available in different versions including community editions and professional editions. You can download any edition of the latest version. Once downloaded, you need to provide login credentials and set up the code. They will provide the link from wherever your code is located, and you have to clone it.

Microsoft Visual Studio provides entity framework which supports both code-based and database-first approaches. Based on these options, we can proceed with implementation. If you choose the database-first approach, all the tables from your SQL database and related components will be created as classes in your C# implementation.

The ROI involves a one-time payment. Once you have the license, the return depends upon how many projects you are acquiring and how many clients you have. If you develop three to four projects, you can achieve ROI within four or five months. With more projects, ROI can be covered within six months or one year based on your investment. After that, you will get more benefits. It is purely based on the projects in the pipeline.

Regarding maintenance, if you have the Microsoft Visual Studio license, Microsoft will support your product. If you encounter any downtime, Microsoft will notify you in advance so you can take respective actions. They provide temporary solutions to ensure applications do not go down. A backup system ensures end users are not affected. The maintenance is provided by Microsoft.

For .NET development, I haven't used any other tools besides Microsoft Visual Studio, but we have used third-party controls to display information, such as Telerik  controls. We obtained the license and integrated Telerik  controls into Microsoft Visual Studio to create data tables and combo boxes. The main competitors to .NET are OutSystems , low-code technologies, and Java.

Debugging  tools are very important. In Microsoft Visual Studio, we can use debugging by placing debug points where we need to execute particular functions or code. When you run the application, Microsoft Visual Studio automatically triggers the debugging point. From there, you can check the particular code in the below window where you can see all values, variables, and written statements. You can track everything. Microsoft Visual Studio provides detailed debugging options to see how the application flows with calling functions and working functions. You can identify exactly where data is not loading and what errors are occurring. This information helps resolve issues quickly. Microsoft Visual Studio provides comprehensive development capabilities. You can create any type of application, including mobile applications, console applications, Windows applications, WPF, ASP.NET  MVC, and .NET Core. It provides many benefits and can create reusable components. During coding, it provides intelligence features that automatically identify issues. It is very user-friendly and helps avoid coding errors.

NA

NA

I use Microsoft Visual Studio  to deploy and migrate different solutions from monolithic to 100% cloud-native solutions in Azure . When I have a client-server solution that is very monolithic, I can perfectly migrate it to Azure  to create backends in different Kubernetes  environments and utilize modern frontend technologies like React for a more efficient solution in cloud platforms.

Microsoft Visual Studio  is a very robust application. I can read and analyze logs in C#. It's friendly with JavaScript, TypeScript, and Java, making many deployments guided for different solutions possible. The .NET library, although very old, is a very robust application for deployment in cloud settings, being friendly for working with functions and logic apps, which are best used for deploying .NET services. Visual Studio offers a great debugging tool where I can debug quickly and resolve issues efficiently with specific solutions designed for strong debugging.

The patching aspect can continue to be improved. Although Visual Studio has very expressive refactor solutions and efficient, reliable patching for code, there is always room for enhancement in these areas.

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

The deployment depends on the project as I use methodologies like Agile or Kanban, allowing the creation of very structured steps in projects. A big deployment can start for three to six months. Locally, when working with Azure, I deploy with Visual Studio on my local machine, integrating with the cloud when I publish.

Microsoft Visual Studio is a very robust and stable application, especially when I have integration with Azure DevOps .

Microsoft Visual Studio is scalable in integrating with various cloud platforms and solutions for effective deployment.

Microsoft's support is very strong, with good resources available when creating support tickets. They respond quickly and have professional resources for resolving different software or deployment issues. A very big library is available at dev.microsoft.com with many solutions for investigation.

Neutral

The initial setup of Microsoft Visual Studio is not complex. I have been using it for maybe 10 to 15 years and it is the most robust application software for deployment.

The ROI depends on the contract I have with Microsoft. For example, in an Enterprise Agreement (ELA), Microsoft might provide free licenses for deployment. The ROI varies based on the company's agreements, and different subscription licenses are available like basic, standard, and business premium.

The pricing for Microsoft Visual Studio is favorable. While many open-source solutions are available, none offer the robustness of Visual Studio, which includes a Marketplace for creating different add-ons and integration solutions for quality assurance.

I have knowledge of NetBeans , an open-source solution, but it does not have the robustness of Microsoft Visual Studio which offers a Marketplace to create different add-ons.

I recommend Microsoft Visual Studio for different clouds as it can integrate with AWS , GCP, Huawei, and Red Hat OpenShift  due to its add-ons. I rate Microsoft Visual Studio a nine out of ten. Despite rating it a nine, all features align well with my personal experience, reflecting no dissatisfaction on my part.

Public Cloud

Microsoft Azure

I develop applications and work at Roma Tre University. We develop applications ranging from student career management to employee and HR office functions.

One valuable feature of Microsoft Visual Studio  is its powerful debugger, which is the only feature I primarily use. Another significant advantage is the integration with Copilot and AI support. Additionally, the ease of integration with solutions is worth mentioning.

Some improvements could include a more visual interface for automating common tasks in application development. Introducing this feature would enhance productivity.

I have been working with Microsoft Visual Studio  for almost ten years.

It is very easy to install Microsoft Visual Studio.

Microsoft Visual Studio is stable overall.

As of now, I have not encountered any limitations in the use of Microsoft Visual Studio. It is scalable for our purposes.

The technical support from Microsoft is very good.

Positive

In my past, I used Mirth Connect while working in a hospital for HL7 integrations using JCAPS and Mirth and Rhapsody Data, which are old products.

It's very easy to install.

I do not know the pricing or costs as we have a global agreement with Microsoft for all universities in Italy.

I am searching for an enterprise service bus product, so if Microsoft Visual Studio could have a plugin or an extension in this direction, it would be great. I rate my overall experience with Microsoft Visual Studio as nine out of ten.

On-premises