Microsoft Visual Studio Reviews

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.

My main use case for Microsoft Visual Studio is writing file processing code and backend APIs.

A specific example of the kind of file processing or API work I do with Microsoft Visual Studio is processing files from the client about their card transactions.

There are no other types of projects or tasks that Microsoft Visual Studio helps me with.

The best features Microsoft Visual Studio offers are the debugging and IntelliSense, which stand out to me the most.

The debugging and IntelliSense features in Microsoft Visual Studio help me in my work because the debugging lets us step through code when we're having issues and the IntelliSense helps us with basic syntax errors.

Microsoft Visual Studio has positively impacted my organization because with Live Share, we were able to collaborate on code projects.

Live Share helped our team collaborate by saving time, improving code quality, and assisting with remote work, as we were able to quickly resolve issues or build features.

I wish Microsoft Visual Studio was available on the Mac for improvement.

I just wish it worked on the Mac.

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

Microsoft Visual Studio is stable.

The scalability of Microsoft Visual Studio is fine; we just install it locally.

I have not needed to contact the customer support team for Microsoft Visual Studio.

Negative

I previously used VS Code and other IDEs before Microsoft Visual Studio, and I switched because Visual Studio just had more fleshed out features.

I wasn't involved in the pricing, setup cost, and licensing, but I'm pretty sure it was free to install.

I have seen a return on investment because Microsoft Visual Studio has saved my team time.

Before choosing Microsoft Visual Studio, I evaluated VS Code and other IDEs.

I would not add anything else about the features of Microsoft Visual Studio.

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

I rate it a seven because you can't use it on all platforms.

My advice to others looking into using Microsoft Visual Studio is that it's free, so try it.

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.

We use the solution to develop applications. 

Microsoft Visual Studio needs to improve integration. 

I have been using the product for five years. 

I rate Microsoft Visual Studio's stability a nine out of ten. 

The tool's deployment is straightforward. It takes less than an hour to complete. 

I can install the solution by myself. 

Microsoft Visual Studio is a free product. 

I rate Microsoft Visual Studio a nine out of ten. 

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.

We use this solution for developing enterprise projects.

It is a beneficial tool because we can write programming code, write our test cases and automate tests in Visual Studio.NET. Additionally, after we develop projects, we can automate and test. It also provides an integrated development environment where we can design our page and program it. It works well both on the front and back end.

The solution could be improved by including an axle intelligence
for tech suggestions and suggesting the dependencies between API. When we use some APIs, we have to add the dependency ourselves in Microsoft Visual Studio. However, with axle intelligence, when an API is added to a project, it can find the dependency of the API and add it automatically.

We have been using this solution for about 17 years now and we are currently using the 2019 version.

The solution is very stable. It works very well once it is open and has never crashed.

The solution is scalable, and scalability depends on what we use the tool for. It has various tools we can use in whatever way we choose. Currently, six people are using this product in our company.

We have had a very good experience with customer service and support.
Whenever we post an issue, someone in the support team reaches out to us within 24 hours. Therefore, I would rate the support team a ten out of ten.

Positive

We used Borland IDE before switching to this solution. Borland C++ builder was a good product then, but we switched to this solution because we think Microsoft Visual Studio is currently the best IDE.

The initial setup is straightforward. It just needs to be downloaded and installed from Microsoft.

We implemented this solution on our own. We work with Microsoft Visual Studio on our PCs, which is installed on every PC. For each project, we have a manager and a group of about five to 60 staff members comprising engineers, administrators and managers. We extend our team and employ new people whenever we get a new project.

Unfortunately, we cannot comment on ROI because we are using the community edition.

Unfortunately, because our country is under hefty sanctions, we could not buy this product so we use the community edition, which is a free version. However, we believe the cost of licensing for this product is logical.

I rate this product a ten out of ten. This product is a very good choice for people searching for an Integrated IDE. Microsoft IDE is very integrated and does not require other tools except Microsoft Visual Studio.NET. However, the product could be improved by including axle intelligence.

It is great for integration with Excel. For example, with Microsoft Access, you can make fast elementary analyses for the business. It is very easy to use.

Microsoft Visual Studio is a powerful product that we can use for visualization. We currently use it for simple business tasks and financial graphics.

The scalability could be improved.

We have been using this solution for more than ten years, and it is deployed on cloud.

The stability depends on the solution that you need. If you use a lot of data, it's not stable, but if you use it for business tasks, it's stable because they are simple tasks.

It is not scalable, and it could be better. About 200 people use Microsoft Visual Studio in my company.

I rate this solution a four out of ten. I would recommend this solution depending on the business case. It is a very simple and nice tool for simple tasks, but I would not recommend it for complex tasks.

I can't speak to performance because it's a cloud solution, and it depends on the cloud. When you are using real-time data, you need the results immediately, so if the cloud is not fast enough, it's an issue. Results aren't provided in real-time, but if it is on-premises, this can be avoided. But if it is on-premises, you must give up some features. Therefore, it is challenging to determine performance.