Microsoft Visual Studio Reviews

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.

I am using Microsoft Visual Studio for developing SQL Server applications.

Using Microsoft Visual Studio has heightened the quality of the work that I do since it is checking everything.

The most valuable feature of Microsoft Visual Studio is its integration with Azure DevOps.

The migration could improve in Microsoft Visual Studio. When I upgraded from 2017 and up to 2022 it was not smooth. There was a lot of manual hand-picking.  Microsoft should put a higher budget for the database developers' section in Visual Studio.

In a future release, it would be a benefit to include an option so I can share the library of methods between different projects in SQL Server easier.

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

Microsoft Visual Studio is a highly stable solution.

We have four or five people using Microsoft Visual Studio in our organization. We are a small startup company.

I have not used the support from Microsoft Visual Studio.

I previously used SQL Server Management Studio which is very popular for development. However, I wanted to source code handling as well, and this is why I moved to Microsoft Visual Studio.

The initial setup of Microsoft Visual Studio was straightforward. However, the difficulty depends on how much of the solution is going to be used. The installation is typically done in smaller steps at the beginning which makes it easy.

The time it took for the deployment was approximately one day.

We did the deployment of the solution in-house but we had a consultant with the GitHub integration.

The solution is expensive.

I rate the price of Microsoft Visual Studio a two out of five.

I am the only person that is needed for maintaining the solution.

My advice to others is to do small steps at the beginning to make it simple. This solution is very large and is best to do it in small steps.

I rate Microsoft Visual Studio an eight out of ten.

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.

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.

I think Microsoft Visual Studio is a good tool.

I think it is very successful and easy to use. I currently do not see any areas to develop. Microsoft Visual Studio is an excellent product.

The stability is fine.

We have a very scalable solution with Microsoft Visual Studio.

We have not had the need to use technical support, but the website has been good.

The initial setup could be more straightforward. After the initial setup, it is easy to use and develop codes in different languages.

A license is required. I think it is a good product, but the price is high. They could sell it at a better price point.

I would rate Microsoft Visual Studio a nine out of ten.

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.

We use it for coding purposes and to integrate the code with the other code. It's helpful to know what bugs are in there.

I like that it works fine and that it performs better than competing products. I'm very happy with Microsoft Visual Studio.

It would be better if it didn't get stuck. Sometimes when we are writing code, we open too many tabs and modules, and it gets stuck.

I have been using Microsoft Visual Studio for about four years.

Microsoft Visual Studio is a stable solution.

Microsoft Visual Studio is a scalable solution.

The initial setup is straightforward. It's not that complex. You can push or pull the code very quickly with some commands. The deployment time depends on how much code you are writing and the internet speed. It won't take much time. For me, on average, we write the code in the morning, and we submit that to the cloud at the end of the day. This takes hardly 15 to 20 minutes.

We use the free version, and you don't need a license. 

Compared to other platforms, this is the best one. I use Python and Anaconda for Python-related things. So, compared to these, I found Visual Studio to be far better as we can install with all the requirements. We can install most of the other things there. 

I would recommend this solution to potential users.

On a scale from one to ten, I would give Microsoft Visual Studio a nine.