Microsoft Visual Studio Reviews

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. 

I am using Microsoft Visual Studio for developing WPS applications.

The most valuable feature of Microsoft Visual Studio is the good intelligence and UI.

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

The stability of Microsoft Visual Studio could improve. There are times it hangs or stops working and I have to restart the program.

The scalability of Microsoft Visual Studio is good.

We have approximately 10 people in our company's automated department using the solution.

Our manager has spoken to the technical support from Microsoft Visual Studio.

Microsoft Visual Studio is easy to set up. The deployment took approximately 30 minutes.

We did the deployment in-house of Microsoft Visual Studio.

This is a good solution for developing .NET applications and other applications.

I rate Microsoft Visual Studio an eight out of ten.

We use Microsoft Visual Studio for development.

The most valuable feature of Microsoft Visual Studio is how easy it is to access all the basic templates for development. There are so many features you get with Visual Studio that it's really helpful for the deployment, the development, and the intelligence behind it. 

The product and its features have come a long way over the years. There are so many features available that you can't use them all. I would like to see more on-premise tips and tools along with development time so that I don't need to go to a third-party site. It would be better if Microsoft Visual Studio familiarized me with all the updates and new feature sets. Help tips would be really helpful.

I would like to see a design preview feature. In the 2013 version and partially in the 2015 version, there was a design screen within Visual Studio. Now, you can't really see the design elements during development without deploying the whole design template. The design preview would be beneficial in future updates.

I have been using this solution for 10 years.

The solution is stable. It has not crashed.

Microsoft Visual Studio is scalable enough for us. Teams work on it and can collaborate on their work. The number of users depends on the strength of the team and the requirements of the project.

The support for Microsoft Visual Studio is good. All the templates for different types of development like Windows, APIs, and Angular development are all supported.

Other than the Microsoft line-up, you can work on the open source languages as well. They support open source languages like Angular and Node.

Positive

Previously we worked with different IDEs. We use Visual Studio in parallel with VS Code in parallel with Atom. We also work with Eclipse. 

I prefer Visual Studio because I am also working with Microsoft Teams.

The initial setup of Visual Studio is straightforward for anyone familiar with the solution. Newer users will experience a learning curve, but it is not because of the GUI, the user experience is good.

We have an enterprise-level license. The cost is expensive for small to medium-sized organizations.

Microsoft Visual Studio is an excellent IDE, but the features are more of VS Code. For small to medium-sized organizations, the licensing for Visual Studio may be too expensive. It is really suited for companies that work on the cloud, or have large teams working on Microsoft Stack. Many open-source tools provide similar feature sets. 

On the other hand, you will find Visual Studio more user-friendly than open source. It has a better GUI and is more plug-and-drop compared to other IDEs.

It is also a personal preference. If you are comfortable with command terms, then Visual Studio provides that. If you require a TFS repository, you do need Visual Studio as an IDE, as they are really tightly coupled and easy to do all your CI/CD. Lastly, if you use a version control other than TFS, then you may prefer a different IDE, like VS Code or an open-source IDE.

The main factor is going to come down to cost. 

I would rate Microsoft Visual Studio an eight out of ten overall.

I use Microsoft Visual Studio to develop software.

What I like the most about Microsoft Visual Studio is that it's useful. It's also a very stable solution, and is scalable as well. It's quick to set up as it only took me a few seconds to do it.

What I don't like about Microsoft Visual Studio is its user interface. It could be better. WebStorm is a better solution for me as it has a good user interface and is more user-friendly, though my friends like Microsoft Visual Studio. I worked with WebStorm for the web layer, and for the server layer, I worked with IBM Eclipse which is my favorite software. I also dealt with JavaScript, HTML, and CSS through Angular.

I've been using Microsoft Visual Studio for four years.

Microsoft Visual Studio is a very stable solution.

Microsoft Visual Studio is a scalable solution.

We use the internet, for example, YouTube sites to solve issues about Microsoft Visual Studio. We don't contact their support team.

The initial setup for Microsoft Visual Studio wasn't complex. It was very easy. The process was easy to understand. It only took me five seconds to deploy Microsoft Visual Studio.

I implemented Microsoft Visual Studio myself. You can do it in-house.

Microsoft Visual Studio is free. It's freeware, so you don't have to pay for its license.

I evaluated WebStorm, IBM Eclipse, and Angular.

In my company, three users work with Microsoft Visual Studio.

I would recommend WebStorm to others, rather than Microsoft Visual Studio.

My rating for Microsoft Visual Studio is six out of ten, though my friends would probably rate the solution a ten.

I'm using Microsoft Visual Studio for developing mobile applications using Xamarin. It's similar to a software development kit (SDK).

The most valuable features of Microsoft Visual Studio are the UI functionality where you can do software development. Everything is available there that you need. You can create the UI, and code, develop and compile it.

Microsoft Visual Studio can improve by adding more features to the Mac version. There are a lot of features lacking in the Mac version, there are limitations. I can install Microsoft Visual Studio on the Mac operating system, but it is not the same as if I installed it on a Microsoft Windows system. The Microsoft Windows version has a lot of features available in Microsoft Visual Studio.

I have been using Microsoft Visual Studio for approximately nine years.

The stability of Microsoft Visual Studio is good.

Microsoft Visual Studio is scalable. I can write a lot of code and there is not any problem with performance.

We have approximately 200 IT department people using this solution in my organization.

When we have an issue we generally put it in the online forum or email to receive a reply. They provide a response within 24 hours, which is good.

The price of Microsoft Visual Studio is approximately $400 annually.

My advice to others is Microsoft Visual Studio is a good tool for development. It is easy to handle and use, and it has a clean UI design. Overall it is not complicated. Anyone can use it to develop any web application or mobile application. It's cross-platform, it can run on Microsoft Windows and macOS. The cross-platform features are good.

I rate Microsoft Visual Studio a nine out of ten.

We use Microsoft Visual Studio for various builds such as building our .NET applications, and in some cases, we use it for design, and for building specifications.

What we like about Microsoft Visual Studio is that it's a comprehensive tool. It has features that work for different plans and it has a wide variety of use cases. It's also a powerful tool and it's quite efficient.

There's always room for improvement in any product, and in Microsoft Visual Studio, it can be spread into other areas of development and design. It's pretty much Microsoft-oriented at the moment. It can be spread into other open source or open source-based developments. That's why I gave it a rating of eight. There's always room for improvement, for example, the UI could be better, and development could be easier on Microsoft Visual Studio if there were more features like drag and drop and more frameworks, etc.

We've been using Microsoft Visual Studio for the past three years.

Microsoft Visual Studio is a stable tool. It has improved in terms of stability.

In terms of scalability, I don't know if scalability applies to Microsoft Visual Studio, to be honest.

We never required technical support from Microsoft Visual Studio because it's a straightforward tool. Online help is great, for example, the community support and forums are all good and widely used.

Microsoft Visual Studio has improved a lot over the years, and setting it up is quite straightforward now.

How fast the tool is deployed depends on project to project, but usually deployment is quite efficient and fast. We usually take on average fifteen days to build a feature and deploy it in DevOps.

We both have an in-house team and partners that take care of the implementation of Microsoft Visual Studio.

I've seen ROI from Microsoft Visual Studio.

The development license for Microsoft Visual Studio is free. I don't know if there's a licensing cost to it.

We evaluated Eclipse and also used other tools, but Microsoft Visual Studio is good.

My company has been using Microsoft Visual Studio for development purposes, particularly Microsoft Visual Studio for .NET development.

I would highly recommend Microsoft Visual Studio to others looking into implementing it. I would also advise that it has some learning curve to use, in particular, people need the technical skill to use the tool properly.

My rating for Microsoft Visual Studio is eight out of ten.

The product integrates well with Azure Cloud, and it supports a ton of languages.

It also has a very good interface for Git source code management. Then there are a couple of add-ins or plug-ins that are out there in the marketplace that sometimes come in handy. From a developer standpoint, it does a very good job when it comes to debugging. It's a great development tool. 

The initial setup was pretty straightforward. 

The solution has good technical support.

It has a ton of options and that sometimes can become very, very overwhelming for a new person, a new developer. If something can be done around simplifying the product, for example, if there's a way, to just have enough options that are relevant for me, that could probably help.

The upgrade system is a bit complex. If they're upgrading something, then they should not force us to go to the next version. Maybe they should probably just release a fix or something that, and once we implement that fix, it gives us at least a choice that you're good for some time even if you don't want to upgrade.

A ton of time is just spent trying to keep ourselves up with the frequent releases that Microsoft rolls out. That is something that takes away from our productive time that we could have invested that time to enhance your application, and could have worked on additional features or functionalities, however, you end up spending that time just to upgrade your current solution to the next version that they roll out.

I've been using the solution for three years, however, my team members have been using it for ten to 12 years now.

In terms of the stability, the frequent upgrades that they roll out and then they force us to upgrade the solution, upgrade the tool itself, those sometimes can be a nuisance.

Most of the time, I see my team members end up spending a lot of time just upgrading the application to the next .NET framework. Or sometimes even the Microsoft Visual Studio version that gets rolled out and then you just have to do that upgrade. Therefore, the frequent upgrades that happen just don't support the older ones, they just take it off support, which causes a lot of nuisance.

The project that I'm part of is a huge team for sure. We are a team of a couple hundred. 

There have been instances in the past where we have reached out to Microsoft.

Support-wise, they're doing a fair job. I don't mind that. Whenever we reach out, we do get help.

It was a pretty easy setup. For us, basically, it comes with some preconfigured settings. The license that we have is a project from our customer. It is fairly straightforward.

We had a third party help us with the initial setup. We did not do it completely by ourselves.

I'm not someone who concerns myself with the cost. That said, my understanding is the license cost is a lot. Before customers roll out a license for any developer, they make sure that it is relevant and it's required for the job. 

We use the enterprise edition of the product. We're using the latest version.

We're end-users of Visual Studio. We're also using Microsoft Teams as well.

We have a couple of applications running on-prem. The roadmap is to move as much as possible onto Azure.

I'd rate the solution eight out of ten.

We use this solution to support a number of different web development processes across different tools and languages. 

This solution can integrate with almost any functionality offered by Microsoft.

We have been using this solution for three years. 

This is a stable solution. 

The initial setup is straightforward.

The pricing for licenses could be reduced to make this solution more competitive.

I would rate this solution an eight out of ten.