Microsoft Visual Studio Reviews

Visual Studio is a tool used for custom software development. It covers everything under this umbrella, including architecture for automation testing. We have between 60 and 70 users working with Visual Studio.

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

Visual Studio is stable enough. There have been some issues but not very often. 

Visual Studio is a development environment. It only runs on one computer. Everyone has their own installation. If we talk about the cloud version, it's scalable. It has served our needs. We plan to increase usage by 5 to 10 percent as our departments grow. 

I have been using Microsoft Visual Studio since .NET first came out. Prior to that, I used tools with other software development languages like Eclipse. Eclipse was an IDE-independent software vendor. 

Installing Visual Studio is easy on average. Sometimes you need to install various libraries, so it depends on your setup. I would say it's medium difficulty.

I rate Microsoft Visual Studio nine out of 10. 

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. 

One of the most valuable features is its support. It's easy for me to get support even though I never use it. If there's a bug or a performance issue, Microsoft also provides quick updates, and this is another valuable feature of the program.

A room for improvement in Microsoft Visual Studio is its performance. Currently, some of our devices are not that capable, so performance still needs to be improved.

An additional feature I'd like to see in the next release of Microsoft Visual Studio to make it better is a more centralized education system, e.g. for Microsoft to put the tutorial for the program under Microsoft Learn.

I've been working with Microsoft Visual Studio for two years, and I'm still using it.

The stability of Microsoft Visual Studio is okay, but it could be more stable.

Microsoft Visual Studio is a scalable program. It's enough for me, and I'm utilizing it a lot, and that's one of the most important things for me.

I'm using my company's equipment, so Microsoft Visual Studio is already set up on it. The program's easy to set up.

I'm using the latest version of Microsoft Visual Studio, e.g. the 2022 version if I remember correctly. It depends on what my company is using.

The most valuable thing about Microsoft Visual Studio is that it's already deployed in my company and used by my company, so I can just use it. That's the reason I'm using the program.

I haven't contacted technical support for Microsoft Visual Studio.

I'm giving Microsoft Visual Studio a rating of 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.

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.

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.

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. 

We use Microsoft Visual Studio for general development, web development, and IT development.

Microsoft Visual Studio is an easy-to-use solution. All recent versions of Microsoft Visual Studio have live code, which allows multiple people to code on the same thing. The other valuable features of Microsoft Visual Studio are the integrations and extensions.

The solution’s technical support could be improved.

I have been using Microsoft Visual Studio for more than ten years.

I rate Microsoft Visual Studio ten out of ten for stability.

Over 1,000 users are using the solution in our organization.

I rate Microsoft Visual Studio a nine out of ten for scalability.

The solution's technical support is average. In some cases, I find it very good, and in other cases not so good.

The solution's initial setup takes a while but is quite straightforward.

We purchased an expensive enterprise version of Microsoft Visual Studio.

Microsoft Visual Studio helps streamline team collaboration. I would recommend Microsoft Visual Studio to other users.

Overall, I rate Microsoft Visual Studio a nine out of ten.

I use the product to develop software. 

The tool is good for interactive testing. It has good integrations and works well for remote services. The product also has features for collaborative work where it allows others to control my screen. It has a good community for every language. 

I have faced configuration issues with Microsoft Visual Studio. 

I have been using the solution for two years. 

The solution is stable. 

I would rate Microsoft Visual Studio's scalability an eight out of ten. 

I haven't reached out to the tool's support. 

Microsoft Visual Studio's setup is straightforward. It is easy to download the solution and you need to allow permissions depending on whether you are a Mac or Windows user.  

I use Microsoft Visual Studio's free version. 

I would rate the tool a nine out of ten. 

We use the solution to write and develop program language and websites.

The solution is user-friendly.

The solution's setup process could be more straightforward.

I have been using the solution for ten years. At present, I use its latest version.

I rate the solution's stability above ten.

We have around 500 solution users in our organization. I rate its scalability above ten.

The solution's initial setup process is complex. It takes a day to complete.

We took help from a consultant to implement the solution.

The solution is worth the investment.

We pay for the solution's license. It could be cheaper.

The solution has good stability and performance. I recommend it to others and rate it a six out of ten. I advise others to understand the process before implementing it.