Microsoft Visual Studio Reviews

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.

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.

I use the Visual Studio Team System for programming. 

My company works with outsourced programmers. The solution helps us to test, integrate and foresee the code quality. We can trace the development stages. 

I like Azure DevOps integration and the nativeness of the C#. 

Visual Studio Team System needs to improve documentation. 

I have been using the solution for ten years. 

I rate the solution's stability a nine out of ten. 

I rate the product's scalability a nine out of ten. 

Visual Studio Team System is expensive, but it is worth the money. 

You can start using the community edition first. I rate the tool an eight out of ten. 

I am using Microsoft Visual Studio for development and C-sharp coding.

In our organization, we use it for debugging while installing and using whatever package we require. Hence, it is an independent platform, which adds to some of its useful features.

The time that it takes to load the application can be reduced. The aforementioned details can be considered for improvement.

I have been using Microsoft Visual Studio for nearly three years. 

It is a stable solution. Stability-wise, I rate the solution a ten out of ten.

It is a scalable solution, and it is very easy to scale. Scalability-wise, I rate the solution a ten out of ten.

There are so many people using it owing to the fact that it is similar to a credit card system.

The solution is suitable for medium enterprises.

The technical support is good. I rate the technical support a ten out of ten since I don't have any issues with the support.

Positive

Previously, I was using HTML Editor for JavaScript coding. I got into development, and that's why I switched to Microsoft Visual Studio.

The installation of the solution is easy.

I don't have any cloud, but there is some setup file available for installation, and I use that.

We use Microsoft VSTS to deploy CI/CD pipelines, so it automatically builds the application and publishes it. Therefore, we don't face any problems.

There are two engineers taking care of the deployment.

The solution doesn't require any maintenance.

I had evaluated some other options. I chose to go with Microsoft since my organization's technology is based on Microsoft, which is why it is easier to work with Microsoft Visual Studio.

Microsoft Visual Studio is a vast application. We need to explore more and make use of it. I would definitely recommend the solution to those planning to use it.

I rate the overall solution a nine out of ten.

I use Microsoft Visual Studio for data modeling. 

I like the product's connection with Azure analytics services and the ability to build the model on the cloud. 

The tool's interface should be more user-friendly. 

I have been working the solution for six months. 

Microsoft Visual Studio Code is not the best in terms of scalability. My company has 15 users for it. 

The product's setup is straightforward. The time taken to deploy it depends on the project. 

I would rate the solution a seven out of ten. 

We use the solution to develop in-house products.

The solution's most valuable feature is its integration with various platforms.

There could be more coding languages in the solution.

I have been working with the solution for two years.

It is a stable solution. I rate its stability nine out of ten.

It is a scalable solution. Presently, five people use it in our organization.

The solution's initial setup is easy. We require a team of 15 executives, one director, five to six managers, engineers, and technical staff for its maintenance.

The system administrators help us implement the solution.

We are using the solution's free version.

I rate the solution a nine out of ten.

I have used Visual Studio in my school to develop small applications for college assignments. It's basically for software development.

I use all healthcare tools. I work with digital care, so I work on integration engines, which are basic. I handle the interface engines. Integration engines are what I'm mostly working on. For example, I'm working a lot with Rhapsody and Mirth.

Visual Studio is used by software developers who develop applications. I am just a consultant. I was just trying to manage my skills and have just used it recently. 

The design feature is really helpful. It's just a drag-and-drop process, which speeds up the design state of the project. I think designing any application is quite precise, and it's easier to do than any other application.

It is pretty simple to set up.

The stability is good. 

For Visual Studio, the only challenge I've faced is referencing any package or new concept I'm trying to debug or run. For example, with Visual Studio, you must import a package if you're doing any specific development. You need to import that package if you're developing a specific programming language. Maybe they could have a framework that includes everything. Sometimes you have to go out of your way and search for a specific package so that you have the code that you need.

It's too soon for me to provide feedback for Visual Studio since I've not been an active user of that software for very long. Maybe they could have documentation that includes everything so the information you need is easy to find.

I've used it maybe for a year, a little more than a year.

The solution is quite stable. There are no bugs or glitches, and it doesn't crash or freeze.

It's just me who's using it right now for my personal use. Of course, it is used widely. I'm pretty sure there are millions of people using Visual Studio.

It's easy to implement. I just did download it from the net. It was quite easy. You just downloaded and install it. It takes maybe an hour.

There is no cost involved. You simply download the solution. 

It is a desktop application. It is not on the cloud. 

I'd recommend the solution to others. It's easy to use.

I would rate the solution eight out of ten.

I write all of my web applications and perform debugs with the solution. Our company is a Microsoft partner and has 1,000 developers and technical team members that are dispersed across the UK, US, and Asia Pacific.

The breakout point, interface design, and coding areas are WYSIWYG and easy to use. 

The solution includes a debug function that I can breakpoint to easily detect what is wrong with my applications. It is really good for debugging C# code. It identifies which lines or sections have problems and if your naming is incorrect.

The solution is not really good at debugging JavaScript, jQuery, or SQL. 

For SQL, sometimes I get alerts that there are non-values or mismatches but the line or section is not identified. I get very generic information with SQL. I have to install ELMAH open source code into our SQL so Visual Studio can track it. 

For jQuery, I have to add the debugger command manually. 

Sometimes, when upgrading the product, certain features are removed even though they are very good like EDMS. There was a VISA for connecting databases and creating an entity framework that would generate connections and pulses. It was removed from the latest release so now it needs to be added manually. I like enhancements but would prefer they not remove features as it makes things more difficult. 

When they release things like .NET Core, the solution becomes unstable. There needs to be a long-term plan because so many versions have been released that some are duplicates. Let's say I'm using .NET Core version 5 and they change it to .NET 5 or 6.0, the releases are too quick and completely duplicated. 

Every new release includes duplicates of features. Some are very useful but when they are duplicated, I have to rewrite or upgrade my code. This makes it difficult for a developer and is not a long-term solution. In one year, I've already spent money to develop my apps, and then I have to upgrade the code again. 

I have been using the solution for 20 years. 

The solution is not very stable and sometimes hangs. 

The solution is scalable and adding users is no problem. 

I rely on internal staff for technical support. I believe Microsoft requires you to register as a customer before you can utilize their support. There's an online forum where you can post questions and get quick replies from other users. 

Setup and use are easy. 

Deployment varies based on the size of your project. 

Small, web-deployed projects take less than five minutes and we are ready to publish the web app to Azure. 

For on-premises, we build the DLL and web package in advance. It takes 20-30 minutes to import because you have to upload to the file server, download the package, and import the application.  

Our company is a Microsoft partner so we only use their solutions. 

If you want to use .NET or C#, then Visual Studio is the best solution. 

I rate the solution a seven out of ten.