Microsoft Visual Studio Reviews

I write all of my web applications and perform debugs with the solution. Our company is a Microsoft partner and has 1,000 developers and technical team members that are dispersed across the UK, US, and Asia Pacific.

The breakout point, interface design, and coding areas are WYSIWYG and easy to use. 

The solution includes a debug function that I can breakpoint to easily detect what is wrong with my applications. It is really good for debugging C# code. It identifies which lines or sections have problems and if your naming is incorrect.

The solution is not really good at debugging JavaScript, jQuery, or SQL. 

For SQL, sometimes I get alerts that there are non-values or mismatches but the line or section is not identified. I get very generic information with SQL. I have to install ELMAH open source code into our SQL so Visual Studio can track it. 

For jQuery, I have to add the debugger command manually. 

Sometimes, when upgrading the product, certain features are removed even though they are very good like EDMS. There was a VISA for connecting databases and creating an entity framework that would generate connections and pulses. It was removed from the latest release so now it needs to be added manually. I like enhancements but would prefer they not remove features as it makes things more difficult. 

When they release things like .NET Core, the solution becomes unstable. There needs to be a long-term plan because so many versions have been released that some are duplicates. Let's say I'm using .NET Core version 5 and they change it to .NET 5 or 6.0, the releases are too quick and completely duplicated. 

Every new release includes duplicates of features. Some are very useful but when they are duplicated, I have to rewrite or upgrade my code. This makes it difficult for a developer and is not a long-term solution. In one year, I've already spent money to develop my apps, and then I have to upgrade the code again. 

I have been using the solution for 20 years. 

The solution is not very stable and sometimes hangs. 

The solution is scalable and adding users is no problem. 

I rely on internal staff for technical support. I believe Microsoft requires you to register as a customer before you can utilize their support. There's an online forum where you can post questions and get quick replies from other users. 

Setup and use are easy. 

Deployment varies based on the size of your project. 

Small, web-deployed projects take less than five minutes and we are ready to publish the web app to Azure. 

For on-premises, we build the DLL and web package in advance. It takes 20-30 minutes to import because you have to upload to the file server, download the package, and import the application.  

Our company is a Microsoft partner so we only use their solutions. 

If you want to use .NET or C#, then Visual Studio is the best solution. 

I rate the solution a seven out of ten. 

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 the solution to develop in-house products.

The solution's most valuable feature is its integration with various platforms.

There could be more coding languages in the solution.

I have been working with the solution for two years.

It is a stable solution. I rate its stability nine out of ten.

It is a scalable solution. Presently, five people use it in our organization.

The solution's initial setup is easy. We require a team of 15 executives, one director, five to six managers, engineers, and technical staff for its maintenance.

The system administrators help us implement the solution.

We are using the solution's free version.

I rate the solution a nine 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. 

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.