Microsoft Visual Studio Reviews

I use Visual Studio to build software for the Microsoft platform.

Visual Studio provides integration with GitHub, and the 2022 version makes it easy to move from one branch to another via the GUI when working on a solution. It also provides a view of how the branches are organized with the code inside the repository. 

Visual Studio's best feature is debugging, which isn't available with any other Microsoft development tool.

There's not much help to deal with issues on Microsoft's official websites.

I've been using Visual Studio since 2005.

Visual Studio is stable 95% of the time, except for an error when refreshing DLLs that requires a restart.

Visual Studio is the best tool available for working on the Microsoft platform, with features that aren't available on any other development tool. I would rate Visual Studio nine out of ten.

We use the Microsoft Visual Studio environment to write code for applications.

The most valuable features of Microsoft Visual Studio are the way we are able to design code, deploy, and test our application. It is easy to move an artifact from the start to the deployment stage. It has well-defined processes that you can integrate with any team. Additionally, the solution is always improving.

Microsoft Visual Studio can improve by bringing back designers. They used to have designers for architecture charts and diagrams. They were able to do things, such as database design. If they can bring them back, it would be great.

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

Microsoft Visual Studio is stable.

Microsoft Visual Studio can scale in terms of expected loads. It is highly scalable.

We have four people who use the solution in my organization.

We were using another solution prior to Microsoft Visual Studio.

Microsoft Visual Studio's initial setup is easy. The process took approximately two to three hours.

We did the implementation of Microsoft Visual Studio in-house. We use one person for the deployment and support of the solution.

We have seen a return on investment using Microsoft Visual Studio. Within a week you can be more proficient and see the value.

You have to be a subscriber with a Visual Studio subscription to use the solution and the organization has to purchase a license that's linked to the account.

My advice to others is they should try Microsoft Visual Studio. They will achieve quicker results in terms of being able to deliver the project compared to the competition.

I rate Microsoft Visual Studio a ten out of ten.

We are using Visual Studio for .NET software development.

One application that we are developing is for the service industry in Ireland. We are trying some PoCs for developing APIs and Web Interfaces using ASP.NET CORE. Once we demonstrate it, we will be developing a full-fledged solution.

Other teams in our organization are currently developing other projects, some of which are going into production in about a month.

This is an IDE for software development using .NET, and there are not many tools like it available. Anything we need to do, development-wise, we use this tool.

Its hard to point the most valuable feature as I see this IDE as a complete package for developers to build software solutions. Live Share, code refactoring, IntelliCode, the debug and diagnosis tooling are all valuable.

There are some features that I have yet to explore and it would be helpful to have more information about what is available and how it works.

I have been using Visual Studio for eight years and still using it.

We use this product on a daily basis and the stability is great. It does depend on the environment and how it is set up, but that is for the developers to learn. We have not had any downtime.

This is a scalable solution. At this time, we have five or six developers who are using it.

I have been in contact with Microsoft's technical support, but not much. When I have issues, I use the community forum. I have found that they respond quickly and I can resolve the problem.

I started learning .NET using Visual Studio and still using. As far as developing .NET solutions are concerned, Visual Studio is all that is needed. I did use Eclipse and Netbeans long back to develop Java solutions.

The initial setup is straightforward.

The Azure deployment is very quick, although we are still following the old method. It is still quick to publish and deploy, taking about five minutes for the on-premises version.

I am not the right person to advise on the pricing and the cost aspect as I just develop solutions using the tool. Although I am not directly involved in pricing, I have heard positive comments about the licensing fees. When our subscription expires, the finance department takes care of it.

The most basic edition of Visual Studio, the Community edition, is available free of charge which is oriented towards students, individual developers and small teams.

This tool is widely used in the software industry. The most recent version, 2019, has a lot of new functionality, some of which I still have to explore. Visual Studio is a developer friendly tool.

My advice for anybody who is considering using Visual Studio is that it is a complete package that contains everything you need for .NET code development.

I would rate this solution a ten out of ten.

We use it for development of internal software projects. I am satisfied with it.

We can easily build solutions with this tool and we can get help from many other resources.

It's a universal solution. I like that I can easily find software developers for it. I can easily find staff on Microsoft forums. Also, we have other components that are running on top of Visual Studio. I like that it is open to other platforms. Finally, there are many many resources for Microsoft Visual Studio and I can easily find support. There is a large knowledge base for it as well.

I would like to see support for rapid application development. For example, if I am developing a new project, I am repeating many similar steps again and again and again. But the platform could do this easily, instead of me. It would save me time. This is something I would like to have in Microsoft Visual Studio, to have it take over repetitive tasks from me.

It's a stable solution.

Scalability is fine.

Technical support is good.

The switch depended on a cost-benefit analysis. It was positive for me.

In this type of solution, application development, there are only a few possibilities. One of them is Microsoft. Another one is Delphi. We chose between just these two solutions. Microsoft was very dominant.

I rate it an eight out of 10 because, as I said earlier, it could have more options to speed up development by handling repetitive tasks. But I would recommend Visual Studio.

When selecting a vendor I look at support and the name of the company.

We use Microsoft Visual Studio to write desktop applications.

The most valuable features of Microsoft Visual Studio are debugging and IntelliSense.

Microsoft Visual Studio could improve by making it faster. Every time they add a new feature or plugin it slows it down. They should allow the user to turn off features they do not use.

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

Microsoft Visual Studio has excellent stability.

There are six software developers using Microsoft Visual Studio.

I have not used the support from Microsoft Visual Studio.

The initial setup of Microsoft Visual Studio is easy.

Each of the six software developers that are using Microsoft Visual Studio self-manages their workstations.

The cost of using Microsoft Visual Studio monthly is approximately $300.

Microsoft Visual Studio is the best development environment out there, but it's also the slowest.

I would recommend others to use Microsoft Visual Studio.

I rate Microsoft Visual Studio a nine out of ten.

It is easy to integrate with GitHub. We integrate with GitHub, and we deploy our solution on our local system. We need this integration for pushing our code. When we were working with Eclipse, we had to write everything in the command prompt, which is a little bit tricky, whereas Visual Studio is very much UI-based and simple. So, it's very easy to integrate GitHub with Visual Studio. It is much easier than Eclipse.

It is also good for debugging.

With the free version, we don't have that much support for Visual Studio. Its support is a little bit less and can be better.

I have recently shifted to Microsoft Visual Studio. Before that, I was working on Eclipse. I switched because of project requirements. Initially, it was a bit difficult to understand the debugging and other functionalities, but once I got familiar with it, I find it much easier than Eclipse. It can be made a bit easier for basic users.

I have been working with this solution for two months.

It is stable.

Its scalability is good. In my team, we have around eight members.

It is straightforward. I don't find it complex. I have also used Eclipse, and when I compare it with Eclipse, it is not that complex. 

I would rate it a seven out of ten.

You can use the solution to do coding and drag and drop. It is easy to install with web documentation. 

Microsoft Visual Studio needs to improve integration. 

I have been using the product for 15 years. 

Microsoft Visual Studio is stable. 

The solution is scalable. 

The tool's deployment is straightforward. Deployment takes between ten minutes to one day. One resource is enough to handle the deployment. 

Microsoft Visual Studio is not expensive. Its licensing costs are expensive. 

I rate the product a nine out of ten. 

Our primary use case for this solution is web design. We use the community version on the desktop app.

The codes and the code areas are valuable features.

I rate this solution a ten out of ten. The solution is good, but additional components such as add-ons could be included in the installation packages because it saves time for the user during installation.

We have been using this solution for a very long time.

The solution is stable, and it has no issues.

The solution is scalable but I cannot comment on the number of people using it within our organization.

I rate the customer service and support team a ten out of ten.

Positive

We previously used SharePoint Designer. However, Microsoft Visual Studio was more robust and interacted better with each component.

The initial setup was straightforward.

We implemented it through an in-house team.

I cannot comment on the prices for licensing, but we are on the community version because many companies cannot afford the license packages for companies. So the licenses could be a little bit cheaper.