Microsoft Visual Studio Reviews

We use Visual Studio for website development and related tasks. It's been quite helpful for us.

From a professional perspective, I've been using Visual Studio since childhood, so I find it very useful. The code analysis tool is particularly valuable as it eliminates the need for manual code reviews. 

Many essential features are built-in, making it a great tool. Additionally, it allows for easy integration with other tools like MS Teams, which enhances its usefulness.

Sometimes, the deprecation of packages can be a challenge. Although Visual Studio provides suggestions when we compile and encounter deprecated packages, it can still be confusing. Even after multiple attempts, we may struggle to fix these deprecated packages and related issues. So, it is one of the areas of improvement in Visual Studio. 

I have been working on a website that I inherited from a client, and when I tried to run it on my system, I discovered that some of the packages were either depreciated or no longer in use. It would be helpful if Visual Studio could suggest and handle such unused packages in a more user-friendly manner.

I am suggesting this as an area of improvement because recently I was working on a bigger client project. The project was functioning correctly on my system but not on another system. Later, I found that some packages were depreciated, which might have caused the issue. However, we couldn't determine the exact reason for the difference in behavior because we used the same ZIP file and the same Visual Studio version. Then, when the person tried to run the same code on her system, it didn't work. It seemed to be related to the deprecated packages. Ultimately, the solution we eventually found was to set up a new system for her, reinstalling Microsoft Visual Studio and related components. 

Another area that could greatly benefit from Microsoft within Visual Studio is unit testing. It's a pain point for every software developer. If Microsoft can provide better tools or features related to unit testing, it would be really helpful. Especially when working on complex projects, writing comprehensive test cases can be time-consuming. However, clients often cannot afford to pay for that additional time in the competitive market. 

So in future releases, having some automation capabilities or built-in support for generating test cases would be great. Although we can integrate third-party automation testing tools, they are often paid solutions. For example, I've noticed the presence of plugins like ChatGPT in Visual Studio Code, but I'm not fully aware of their capabilities. Therefore, if Visual Studio could offer some level of automation for test cases, it would be a valuable addition. 

I have been using Microsoft Visual Studio for over 15 years. 

I would rate the stability of Visual Studio a ten out of ten.

Microsoft has gained a lot of confidence in the market, so I would rate the scalability of Visual Studio around eight out of ten.

Based on my recent experience, sometimes, we faced difficulties with the same set of codes. Therefore, considering the recent incident, I leaned toward an eight and not a ten for scalability. 

In my company, around 20 people are using this solution.

The initial setup is very simple. Microsoft has made it very easy to set up.

Price-wise, it is good. We are using the paid versions, and the price is reasonable. For our company, it's a genuine price.

I have only worked with Visual Studio. 

Overall, I rate it a ten. It's very user-friendly and feature-rich.

However, there's always room for improvement in the product. Features like automation test cases to meet market requirements would be beneficial.

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. 

We use the solution for Windows applications and different .NET features. We also use the BI tools.

I like the design tools. Nowadays, it is very advanced. We can use different .NET features.

We have different platforms available for web development. The solution must provide user-friendly features. We get updates frequently. Multiple versions are released within a short period. We need to keep updating the solution.

I have been using the solution for more than ten years.

I rate the tool’s stability an eight out of ten. We need to consider a lot of things while creating projects on Visual Studio. There are a lot of dependencies to add and maintain.

The tool is scalable. There are more than 1000 users in our organization.

We have used Microsoft’s support for SQL Server Reporting Services. Sometimes, we do not receive prompt responses. We have to work with different teams and need to wait for resolutions.

The setup is straightforward. We update the product when we get information from our teams.

The deployment can be done in-house.

The solution has benefited us. The users are really happy to use the product for reporting purposes. It has many features.

I recommend the solution to others. Overall, I rate the tool an eight out of ten.

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. 

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.