Microsoft Visual Studio Reviews

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. 

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.

Currently, in my daily work, I am using Visual Studio to develop different tools. Also, I am trying to use DevOps to manage code and different work items.

It's an excellent tool in general. There are a lot of features that are very, very nice in Visual Studio. 

We can publish directly to the premise's servers. I was testing how to publish in a cloud using Azure and it was very easy. There are a lot of good features in Visual Studio and I'm sure we can add different add-ins or add-ons to make it a little more functional as well.

We can manage our code directly via the repository. We are trying to manage the code in DevOps. With Visual Studio, we can connect to DevOps and manage the different versions that we have using the repository.

You do need to do some training in order to really take advantage of the solution.

Currently, we have issues when Visual Studio has updates. When Visual Studio has updates, right now we have issues in terms of updating our repositories. That was the current issue that we have. We need to update Visual Studio, however, we also need to update continuously the Visual Studio version due to the fact that if we don't update the Visual Studio, we have different problems that follow us.

The initial setup can be a bit complex. 

The thing that is very important is to manage your requirements and the features that you need to develop using Visual Studio. DevOps has that feature available. When we connect Visual Studio or a project with DevOps, we can manage different work items. They could improve that feature, to manage the work items requirements and different things a bit better.

I've used the solution since about 2012, across two different companies. 

It's a stable solution We don't really deal with bugs or glitches. I don't find that it crashes or freeze. It's reliable. 

We've found the product to be scalable. If a company needs to expand it out they can do so. 

We have about 15 people using it regularly right now. 

I'm not sure if we intend to expand usage just yet. We are already, this year, planning to migrate some tools to the cloud. That said, we don't know if we are going to need a little more support or people to do that.

Currently, we use different documentation that exists on the internet to assist us with troubleshooting. We currently use the Microsoft or Visual Studio page to research different functionalities or different features that we need to implement or we need to add to our project. So far, that's been quite helpful.

Initially, it was a little complex to set up. We needed to learn the different features that we could manage in Visual Studio. Right now, as we have had some time to pick things up, it's very straightforward to use.

In terms of deployment, for example, yesterday, I implemented a new version for one of the plants that we have. The tech was immediately published as we are able to use an option to publish the code. We only select the new version and automatically the code is published. It's very fast to publish a new version for the different tools that we have. In that sense, it doesn't take long to deploy.

Each developer is responsible for publishing his own tools and doesn't require another special group or another special people to deploy the tools that we are managing.

Regarding the licensing, I don't manage that. The license is updated each time that it's required to be as the company where I am working, requires that. I don't know if the license is updated monthly or annually, however. It may be annually. 

We're customers and end-users.

While this solution is currently on-premises, the plan is this year try to migrate some tools to the cloud using Azure.

I'd advise new users that it's important initially to do some training to implement Visual Studio. If there are people trying to implement Visual Studio in the company, it's very important to consider the training that will be involved and not just the licensing costs. 

I'd rate the product at a nine out of ten. It's a good solution.

We use it for project development, including tasks such as web API, hosted services, mini-tests, and more.

The valuable feature is that it provides a basic template for everything and built-in debugging tools. They definitely save me time.

Compared to 2019, the 2022 version runs much smoother. The older version used to freeze if I had too many consoles open. The 2022 version is lighter and performs significantly better. Also, the ID itself is quite lightweight.

The UI is fine; they've kept it consistent for a while now, so it's familiar.

The hot reload feature is good, but sometimes it doesn't work. It could be improved. 

Also, the solution is heavy. If it could become lighter, it would attract a larger user base.

I have used the solution since 2008, so for the past 15 years. I’m currently using the latest version from 2022.

The solution is highly stable. I rate it a nine out of ten, with ten being the highest.

If you have multiple windows open, up to three is fine. However, when you exceed three windows, especially on individual laptops, it tends to slow down the system. It is heavy; it is not a light solution. 

We have around ten users for the solution.

The setup process is straightforward, the only thing is the downloadable file is a bit large in size. The deployment process is quite simple. 

You just need to download the file, double-check it, have an administrator, and you're good to go. It takes approximately 20 minutes to complete the setup.

It can be implemented in-house. We have to keep the updates running; that is it. There is no other maintenance required. 

I would rate the solution a seven on a scale from one to ten, with one being the most affordable and ten being the most expensive.

I recommend the solution to all. It enhances productivity. Overall, I rate the solution a nine 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 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 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.

It's mainly used for development. Therefore, it's mainly for either developers or IT development companies where they produce products and then sell them.

It's great for when you want to do development, such as on an enterprise-size project that requires a lot of teams also to be working on that project and that It's also good for helping with the workflow of the development in general.

It's mainly for the organizations that are working on development. First of all, of course, it helps the organization due to the ease of use. It's been a legacy application. It's been working for years and it is already integrated with the cloud.

It's used to provide the support to develop on multiple platforms, whether it is computer devices, web, cloud, or even mobile applications with the same IDE, which is the Visual Studio itself. 

It's a very easy-to-use product.

The support is great. The community and the documentation support for it are great. Whatever you are missing, you are going to find it at Microsoft help.

It's easy to set up.

The stability is good.

You can scale it well.

It would be great if they added some extra support for other languages that are available in the market and prepared it for the, let's say, crypto developers as we are going in the age of cryptocurrency.

If it was more friendly for the simple or starter developer, it would be great. It's friendly anyway, however, it would be better if there was a way to enhance it in a much more usable way as a user-experience type for the new customers or newbies who want to enter the technology.

I've been using Microsoft Visual Studio since the early versions of VB6, which is like in 2006 or 2005.

The stability is great. There aren't bugs or glitches. It doesn't crash or freeze.

The product, since it supports DevOps and is connected to the cloud, is scalable. It can take on many users. It's a per-user installation. It's not a server application. It's a computer-based application. 

There is a new version of it. I didn't try it yet, however, it is fully over the cloud where the development happens on the cloud in Azure. Since I didn't try it, I can't comment on that.

The support is great and so is the supporting documentation. You can easily find answers to your questions. We've very satisfied with that.

Usually, whenever I faced an issue in the past, it would take one to two working days maximum to get assistance. If it was on Azure and you've had a problem on Azure with the server, then it's going to take as much as one day, as it's going to be distributed to the team that is responsible for the region that you are opening the ticket from.

The product is so easy to set up. The only thing you do usually with Microsoft Visual Studio is to go to the internet and download the installer for it. Then it will download the required files and everything from the internet for you, and you go through the installation like any normal program.

The length of time it takes to deploy depends on the features. Visual Studio comes with so many features. It depends on if you are going to choose only Windows development or Windows and mobile development and so on. However, it really depends on the features that you are going to require.

It also depends on the internet speed, as each feature requires extra downloads from the internet. 

Usually, I deploy it for my team. I started a company also that provides services for IT companies. What we do is, if they want a development environment and they don't have anyone, then we install it.

The licensing is per user. 

There is also the Community Edition which users can access as a start for a small application. It's for open-source applications. That's where they build out the support for the open-source community.

There are also Professional or Enterprise options. Which would be the best option depends on the capacity and the requirements of the company that is going to use it. The licensing is affordable for companies, not for individuals. It's not for personal usage.

We provide Microsoft products to customers.

We are using the 2019 version. I know that they have been planning or they already did create a new version of it, however, the last one was 2019.

I would rate the solution at a nine ot of ten. There is always room for improvement, however, we've been quite happy with it so far.