Microsoft Visual Studio Reviews

We use Microsoft Visual Studio for developing our software solutions. We identify gaps in the market and build solutions to address those challenges. Our operations are based in Nigeria, and our development primarily supports the Windows platform.

Visual Studio's collaborative features with Azure DevOps are valuable to us. It allows various team members to collaborate on the same project, maintain consistency, and deliver products that fulfill client promises. We use Azure DevOps for source code repository, enabling synchronization and consistency. Additionally, the integration of AI and enhanced refactoring in the IDE boosts coding efficiency. The suggestions make coding easier, thus improving productivity and reducing errors.

Refactoring in Microsoft Visual Studio could be further optimized. While it is better than before, some third-party tools currently outperform it but come at a cost.

We have been using Microsoft Visual Studio for around twenty years, starting from the early days of Visual Basic to .NET and now .NET Core.

The initial setup of Microsoft Visual Studio is extremely easy. It is a breeze for our developers, and there have been no reported issues with the setup.

Microsoft Visual Studio is highly stable. I have not received any negative feedback from our developers regarding stability.

Based on our use, Microsoft Visual Studio has a high level of scalability. I would rate it as nine.

We have always used Microsoft Visual Studio for development. It came naturally with what we were comfortable using from the start.

The initial setup is very easy. There have been no challenges, and developers find the process straightforward.

Developers install Microsoft Visual Studio on their work machines, and they take ownership from that point. There have been no maintenance needs reported.

Our investment in Microsoft Visual Studio is affected by the economic conditions in Nigeria. We invest in developer certification, but pricing products in local currency can be challenging due to the initial investment in technology acquired in dollars.

We have subscriptions with Microsoft, and although it would be ideal to have it for free, we understand the need for fair pricing, which I rate as five or six.

Not really. The decision to use Microsoft Visual Studio was based on its acceptance and availability at the time the company started.

I would rate Microsoft Visual Studio overall as nine. Our limited use of its components and features satisfies all our requirements. No functionality we needed was unmet. It fits our needs well. The overall product rating would be nine out of ten.

On-premises

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 use Microsoft Visual Studio occasionally. I prefer writing code directly on Notepad++, but when I need the IDE support, I use Microsoft Visual Studio for faster and better code development. It offers a good experience for individuals who are handy with IDEs.

Microsoft Visual Studio is integrated with all tools and offers all necessary extensions, making it very convenient. It offers Git connectivity for all Git repositories. I find all its activities to be straightforward and efficient.

Maybe some documentation could be better. They can generate some educational videos online, which would be helpful.

I have been using Microsoft Visual Studio for the last five to six years, but I do not use it frequently.

Microsoft Visual Studio is stable. I have not encountered any problems.

I use Microsoft Visual Studio on an individual basis, so I am not familiar with its scalability in terms of adding or deleting users, which may be an IT admin function.

I use Notepad++ more often than Microsoft Visual Studio.

The installation of Microsoft Visual Studio is simple, and one person can manage it.

The ROI includes time savings, which are approximately ten to twenty percent.

As a partner, the cost may be part of an integrated license package. I am not sure about specific pricing details.

Maybe sometimes Microsoft Visual Studio hangs if your computer resources are limited. Rating it, I would give it eight points overall.

I create my site or application for my company for internal use only.

The best feature of Microsoft Visual Studio for debugging applications is IntelliSense, which I refer to as autocomplete. Additionally, the integration capabilities with Microsoft DevOps Server streamline my development process efficiently, making it perfectly integrated with Microsoft Visual Studio.

The software has become larger than before, requiring a powerful desktop or notebook to run Microsoft Visual Studio. I must use or install all the features which makes Microsoft Visual Studio bulky. Some optional installation methods to remove features I do not use could improve the experience.

I have been using it for more than fifteen years.

Performance is a problem because if I use a notebook that is not high-end, Microsoft Visual Studio may experience lag sometimes.

I think the support could be better because the documentation and other resources, such as videos, are too numerous, making it hard to find the correct one. AI support could be a good addition.

Neutral

I used Microsoft Visual Studio Code and no others.

There is no trouble or problem to install it. I can handle the installation myself.

I can install the solution by myself.

Microsoft Visual Studio saves me time, approximately forty percent.

Microsoft Visual Studio is expensive.

The main concern is that the documentation is so detailed and vast that it takes a lot of time to sift through. I would rate Microsoft Visual Studio seven out of ten.

My first use case was to develop Microsoft Windows tools in .Net Framework (formerly from 3.5). Later I developed web platforms in ASP .NET and lately, I have developed APIs in both .NET Framework and NET Core, the latest in NET 6.

The platforms that I develop in Windows environments and do not have CI/CD systems I deploy them directly from Visual Studio. The entire Windows ecosystem is well managed by Visual Studio.

When I program in Microsoft Windows I usually use Visual Studio.

Microsoft Visual Studio is a must-have tool if you work in Windows environments.

Organizations working on a large number of workstations or organizations that are just starting out have a complete tool for use in several versions, most popularly free. So starting or developing a project under these conditions is extremely affordable.

But back to the main feature, with Microsoft Visual Studio you have a Swiss army knife of software development (integration, development, debugging, and deployment) complete and free in its most popular version.

The features I found most valuable are those related to the Microsoft Windows ecosystem. The famous umbrella that Microsoft extends over its products.

Working with Azure or SQL Server (connect, implement, deploy, etc.) is extremely easy, a common feature in all Microsoft products.

Deploying to Azure or Windows Server with IIS is also extremely easy and enjoyable.

Finally, integration with Git has improved a lot in the latest versions, as well as integration with GitHub and Copilot.

Efficiency is the main focus. Since Visual Studio's inception, it has been a race of constant improvements and attempts to improve the efficiency of the tool in every release. However, crashes and freezes are common when you work with the tool for a long time. The problems get worse when you have more than one project under development and then you need a very powerful computer to be able to perform complex developments. Even having a very powerful computer, as in my case, does not prevent you from having freezes from time to time.

Long installation or upgrade times are sometimes a problem.

I've used the solution for more than ten years.

I had previously tried other environments such as Atom or Sublime Text, but none offered the capabilities of Microsoft Visual Studio.

The most popular version of Microsoft is the Visual Studio 2022 Community Edition. Making it free gives it a boost in all types of organizations.

I had previously tried other environments such as Atom or Sublime Text. Lately, Visual Studio Code has become very popular and I used it eventually.

My main use case for Microsoft Visual Studio is prototyping different products, different features, and functionality. For example, I have used Microsoft Visual Studio for prototyping by creating a database layer to some app builder. I do not work on other types of projects or features with it.

The best features Microsoft Visual Studio offers are its relatively easy usability and pretty good debugging features.

When I mention the debugging features, a particular function within Microsoft Visual Studio's debugger that stands out to me is how you can attach to running processes, stop the code, and see what's happening, including the status of variables and other information.

Microsoft Visual Studio has positively impacted my organization by providing a standardized interface, making it easy to collaborate across teams. It's easy to help other people out or get help because everybody knows it. Having that standardization has indeed led to measurable improvements; it makes onboarding fast because it's somewhat of a standard that everybody knows. So it's easy for everybody to get into it and start working.

I think Microsoft Visual Studio can be improved because sometimes the setup can be a little bit complicated and it seems sometimes a little bit bloated, with a large download for what it is. There is nothing about performance, usability, or updates that needs to be discussed.

I have been using Microsoft Visual Studio for over ten plus years.

Microsoft Visual Studio is stable.

From my perspective, I cannot really answer about Microsoft Visual Studio's scalability because I only run one instance, but it seems to be scaling fine if the entire company is using it.

I have never used customer support for Microsoft Visual Studio; I always just go online and search if I have any questions.

I did not previously use a different solution before Microsoft Visual Studio; we kind of always used that.

From my side, Microsoft Visual Studio certainly saves time because I know it, so it's easier for me to use; from a company perspective, I cannot really know the metrics.

I do not really handle pricing, setup cost, and licensing because that is managed through the corporate; I'm not dealing with this. For private use, the free version worked pretty well when I used it, although it was missing some vital features.

Before choosing Microsoft Visual Studio, we did not evaluate other options; we always use Microsoft Visual Studio.

My advice to others looking into using Microsoft Visual Studio is to know that there's a lot of information about it out on the internet, so if you run into any issues, you can easily look it up. I gave this review a rating of eight out of ten.

On-premises

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.

Private Cloud

Microsoft Azure

The platform's use cases depend on the entire system diagram. For instance, if we have login software, it determines the users' access level. It helps admin users in uploading and managing user accounts. Other users can register, validate passwords, save, download, and upload tasks.

The system can efficiently manage the databases.

They could add new modules to the platform for enhanced functioning. If we have a new system, we can add new features and improve the product to make it better than the previous system.

I have been using Microsoft Visual Studio's latest version, 6.0, for two years.

Visual Studio is stable.

It is a scalable platform.

Previously, we used Sublime for backend connectivity. We switched because Sublime is a basic and not a standard tool for companies. We can create only small projects using it. However, Microsoft Visual Studio is an open-source tool that offers a lot of technologies. With its help, we can develop applications in various languages, create Windows or iOS software, and even build console applications.

The setup process is easy if we are already working on a project. It is complex if we want to create a new project from start to end. The time taken for deployment depends on what kind of project we are working with. In case of any queries, we refer to YouTube videos, ChatGPT, and Google to find the solutions.

I'm using the platform's open-source version.

If you're working on a simple project, Microsoft Visual Studio might be more than you need. You can go for it if you plan to create bigger software. It offers a wide range of built-in features. I rate it a nine out of ten.