Microsoft Visual Studio Reviews

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.

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.

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.

We use Microsoft Visual Studio for various builds such as building our .NET applications, and in some cases, we use it for design, and for building specifications.

What we like about Microsoft Visual Studio is that it's a comprehensive tool. It has features that work for different plans and it has a wide variety of use cases. It's also a powerful tool and it's quite efficient.

There's always room for improvement in any product, and in Microsoft Visual Studio, it can be spread into other areas of development and design. It's pretty much Microsoft-oriented at the moment. It can be spread into other open source or open source-based developments. That's why I gave it a rating of eight. There's always room for improvement, for example, the UI could be better, and development could be easier on Microsoft Visual Studio if there were more features like drag and drop and more frameworks, etc.

We've been using Microsoft Visual Studio for the past three years.

Microsoft Visual Studio is a stable tool. It has improved in terms of stability.

In terms of scalability, I don't know if scalability applies to Microsoft Visual Studio, to be honest.

We never required technical support from Microsoft Visual Studio because it's a straightforward tool. Online help is great, for example, the community support and forums are all good and widely used.

Microsoft Visual Studio has improved a lot over the years, and setting it up is quite straightforward now.

How fast the tool is deployed depends on project to project, but usually deployment is quite efficient and fast. We usually take on average fifteen days to build a feature and deploy it in DevOps.

We both have an in-house team and partners that take care of the implementation of Microsoft Visual Studio.

I've seen ROI from Microsoft Visual Studio.

The development license for Microsoft Visual Studio is free. I don't know if there's a licensing cost to it.

We evaluated Eclipse and also used other tools, but Microsoft Visual Studio is good.

My company has been using Microsoft Visual Studio for development purposes, particularly Microsoft Visual Studio for .NET development.

I would highly recommend Microsoft Visual Studio to others looking into implementing it. I would also advise that it has some learning curve to use, in particular, people need the technical skill to use the tool properly.

My rating for Microsoft Visual Studio is eight out of ten.

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 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.

The product integrates well with Azure Cloud, and it supports a ton of languages.

It also has a very good interface for Git source code management. Then there are a couple of add-ins or plug-ins that are out there in the marketplace that sometimes come in handy. From a developer standpoint, it does a very good job when it comes to debugging. It's a great development tool. 

The initial setup was pretty straightforward. 

The solution has good technical support.

It has a ton of options and that sometimes can become very, very overwhelming for a new person, a new developer. If something can be done around simplifying the product, for example, if there's a way, to just have enough options that are relevant for me, that could probably help.

The upgrade system is a bit complex. If they're upgrading something, then they should not force us to go to the next version. Maybe they should probably just release a fix or something that, and once we implement that fix, it gives us at least a choice that you're good for some time even if you don't want to upgrade.

A ton of time is just spent trying to keep ourselves up with the frequent releases that Microsoft rolls out. That is something that takes away from our productive time that we could have invested that time to enhance your application, and could have worked on additional features or functionalities, however, you end up spending that time just to upgrade your current solution to the next version that they roll out.

I've been using the solution for three years, however, my team members have been using it for ten to 12 years now.

In terms of the stability, the frequent upgrades that they roll out and then they force us to upgrade the solution, upgrade the tool itself, those sometimes can be a nuisance.

Most of the time, I see my team members end up spending a lot of time just upgrading the application to the next .NET framework. Or sometimes even the Microsoft Visual Studio version that gets rolled out and then you just have to do that upgrade. Therefore, the frequent upgrades that happen just don't support the older ones, they just take it off support, which causes a lot of nuisance.

The project that I'm part of is a huge team for sure. We are a team of a couple hundred. 

There have been instances in the past where we have reached out to Microsoft.

Support-wise, they're doing a fair job. I don't mind that. Whenever we reach out, we do get help.

It was a pretty easy setup. For us, basically, it comes with some preconfigured settings. The license that we have is a project from our customer. It is fairly straightforward.

We had a third party help us with the initial setup. We did not do it completely by ourselves.

I'm not someone who concerns myself with the cost. That said, my understanding is the license cost is a lot. Before customers roll out a license for any developer, they make sure that it is relevant and it's required for the job. 

We use the enterprise edition of the product. We're using the latest version.

We're end-users of Visual Studio. We're also using Microsoft Teams as well.

We have a couple of applications running on-prem. The roadmap is to move as much as possible onto Azure.

I'd rate the solution eight out of ten.

We use it mostly for build management.  

Visual Studios is a business solution developed by Microsoft. In general, I like it because it integrates many tools into one interface to provide a total solution. I think it is convenient to have everything in one interface.  

I think that because it integrates many tools into one interface the startup is very slow. It would be nice if the startup speed could be improved. Maybe in the future, they can provide a better, lighter interface or something based in the cloud. It would be on Azure, for example, or other cloud providers. But I do not think Microsoft will have native support with AWS.  

We have not only purchased the Visual Studio, but we also subscribed to MSDN (Microsoft Developer Network). I like that this way we can always have the latest updates. All the products from Microsoft always have the most up-to-date functionality.  

I have been using Microsoft Visual Studio for 15 years.  

It is amazing sometimes that Visual Studio will pop up a message reminding me about the performance. Sometimes it will tell me how much time it is spending on certain tasks. Microsoft suggested I disable this feature, but I cannot disable it, so I have to let it post the reminders and alerts.  

What I want to have is more scalability. If Microsoft can provide more possibilities for scalability that would be better for me. Sometimes I do not need it, but sometimes I think I need it. I want it to be easy to configure and easy to add our demos.  

Hundreds of users are using this product within our company.  

With technical support, we have the benefit of raising a ticket if we get stuck on something in progress. We can create a ticket with Microsoft with specific questions or problems to get their help in working through any technical issues. They are pretty good with their response.  

When I came to work in this company, the company had already decided to use this tool. So I have to use this tool for development when working here because it is what was available for development.  

The company buys and pays for the product. I think our purchasing department gets a fair price for it. But the actual price is something I do not have any idea of.  

I think how the product gets used and how it fits your use case depends on different user scenarios in the development environment. I cannot say which tool is better for someone in their circumstances. If someone wants to use the open-source to get free development resources, I think that is also an okay solution, but they may need to spend more time on making anything integrated with other OSS (Open Source Software) or OTS (Off-The-Shelf Software) software.  

I would recommend this product, but it depends on the user's scenario and the user environment. I cannot easily say if another user can easily accommodate Microsoft Visual Studio or not.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate Visual Studio as a seven or eight-out-of-ten.