Microsoft Visual Studio Reviews

I use Microsoft Visual Studio to develop software.

What I like the most about Microsoft Visual Studio is that it's useful. It's also a very stable solution, and is scalable as well. It's quick to set up as it only took me a few seconds to do it.

What I don't like about Microsoft Visual Studio is its user interface. It could be better. WebStorm is a better solution for me as it has a good user interface and is more user-friendly, though my friends like Microsoft Visual Studio. I worked with WebStorm for the web layer, and for the server layer, I worked with IBM Eclipse which is my favorite software. I also dealt with JavaScript, HTML, and CSS through Angular.

I've been using Microsoft Visual Studio for four years.

Microsoft Visual Studio is a very stable solution.

Microsoft Visual Studio is a scalable solution.

We use the internet, for example, YouTube sites to solve issues about Microsoft Visual Studio. We don't contact their support team.

The initial setup for Microsoft Visual Studio wasn't complex. It was very easy. The process was easy to understand. It only took me five seconds to deploy Microsoft Visual Studio.

I implemented Microsoft Visual Studio myself. You can do it in-house.

Microsoft Visual Studio is free. It's freeware, so you don't have to pay for its license.

I evaluated WebStorm, IBM Eclipse, and Angular.

In my company, three users work with Microsoft Visual Studio.

I would recommend WebStorm to others, rather than Microsoft Visual Studio.

My rating for Microsoft Visual Studio is six out of ten, though my friends would probably rate the solution a ten.

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.

I use Microsoft Visual Studio for data modeling. 

I like the product's connection with Azure analytics services and the ability to build the model on the cloud. 

The tool's interface should be more user-friendly. 

I have been working the solution for six months. 

Microsoft Visual Studio Code is not the best in terms of scalability. My company has 15 users for it. 

The product's setup is straightforward. The time taken to deploy it depends on the project. 

I would rate the solution a seven out of ten. 

I am using Microsoft Visual Studio for developing WPS applications.

The most valuable feature of Microsoft Visual Studio is the good intelligence and UI.

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

The stability of Microsoft Visual Studio could improve. There are times it hangs or stops working and I have to restart the program.

The scalability of Microsoft Visual Studio is good.

We have approximately 10 people in our company's automated department using the solution.

Our manager has spoken to the technical support from Microsoft Visual Studio.

Microsoft Visual Studio is easy to set up. The deployment took approximately 30 minutes.

We did the deployment in-house of Microsoft Visual Studio.

This is a good solution for developing .NET applications and other applications.

I rate Microsoft Visual Studio an eight out of ten.

We use Microsoft Visual Studio for development.

The most valuable feature of Microsoft Visual Studio is how easy it is to access all the basic templates for development. There are so many features you get with Visual Studio that it's really helpful for the deployment, the development, and the intelligence behind it. 

The product and its features have come a long way over the years. There are so many features available that you can't use them all. I would like to see more on-premise tips and tools along with development time so that I don't need to go to a third-party site. It would be better if Microsoft Visual Studio familiarized me with all the updates and new feature sets. Help tips would be really helpful.

I would like to see a design preview feature. In the 2013 version and partially in the 2015 version, there was a design screen within Visual Studio. Now, you can't really see the design elements during development without deploying the whole design template. The design preview would be beneficial in future updates.

I have been using this solution for 10 years.

The solution is stable. It has not crashed.

Microsoft Visual Studio is scalable enough for us. Teams work on it and can collaborate on their work. The number of users depends on the strength of the team and the requirements of the project.

The support for Microsoft Visual Studio is good. All the templates for different types of development like Windows, APIs, and Angular development are all supported.

Other than the Microsoft line-up, you can work on the open source languages as well. They support open source languages like Angular and Node.

Positive

Previously we worked with different IDEs. We use Visual Studio in parallel with VS Code in parallel with Atom. We also work with Eclipse. 

I prefer Visual Studio because I am also working with Microsoft Teams.

The initial setup of Visual Studio is straightforward for anyone familiar with the solution. Newer users will experience a learning curve, but it is not because of the GUI, the user experience is good.

We have an enterprise-level license. The cost is expensive for small to medium-sized organizations.

Microsoft Visual Studio is an excellent IDE, but the features are more of VS Code. For small to medium-sized organizations, the licensing for Visual Studio may be too expensive. It is really suited for companies that work on the cloud, or have large teams working on Microsoft Stack. Many open-source tools provide similar feature sets. 

On the other hand, you will find Visual Studio more user-friendly than open source. It has a better GUI and is more plug-and-drop compared to other IDEs.

It is also a personal preference. If you are comfortable with command terms, then Visual Studio provides that. If you require a TFS repository, you do need Visual Studio as an IDE, as they are really tightly coupled and easy to do all your CI/CD. Lastly, if you use a version control other than TFS, then you may prefer a different IDE, like VS Code or an open-source IDE.

The main factor is going to come down to cost. 

I would rate Microsoft Visual Studio an eight out of ten overall.

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 Visual Studio for development and for projects using VS Code and Visual Studio Code.

The most valuable aspect of this solution is the integrated development environment. It also offers a very good integration with Microsoft Cloud.

This solution could be integrated with other open-source languages, such as Python and not only C#, .NET or Microsoft development languages.

We have been using this solution for two years.

This is a scalable solution. Scalability is not such an important parameter for us because we use this solution as a development tool.

We use NetBeans for Java development. When I compare NetBeans with Visual Studio, Visual Studio is more professional than NetBeans.

The initial setup is straightforward and took less than half a day. 

Yeah, of course. We work to use the Professional Visual Studio, because they have some capabilities for CI/CD pipeline. For that reason, in the future, maybe six months later, we will start to use Visual Studio Professional.

I would rate this solution 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.