Microsoft Visual Studio Reviews

I use the reporting portion of Microsoft Visual Studio.

I would like to have more integration with other platforms and technologies.

I have been using Microsoft Visual Studio for about two years now.

I have found that it is scalable. We have some old products and we have a standard expansion platform. As far as scalability goes, I have done a lot of work with access and reporting, finding ways to upgrade the old systems and old platforms, with some newer versions, or migrate to other systems. 

I use technical support for database questions.

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

My primary business is designing architecture, and I use Visual Studio to demonstrate how to use VS code in the browser. For example, if someone has a business idea for a banking application and is starting to think about how to develop it, they can use Visual Studio to make a very quick prototype. The pipelines then deliver this project to the new environment, and the end-user can see how quickly the application works.

Visual Studio improves communication between teams, which saves valuable time.

The most valuable feature is the lightweight cross-platform support and the robust architecture. You can easily create, edit, and test any software and develop applications for all the major platforms, including cloud, desktop, and mobile.

Visual Studio could be improved with the ability to personalize the interface and development style and to edit extension requirements.

Visual Studio is a very good, very convenient, very powerful development solution. I would rate it as nine out of ten.

Our primary use case of this solution is for performance testing.

The feature I find most valuable is the fact that it's broad-spectrum, so it can be used for a wide variety of technologies. We are predominately .NET based and we use mostly .NET Core or .NET Framework so I can call in any immediate packages.

I would only say the deployment outline can be improved. We have shifted away from using Team Foundation Server, because it didn't work for our company. We shifted over to the Git approach and I do know that the Team Foundation Server has Git support. But we decided to rather go with GitLab as our main platform. 

In terms of more support I would like to have the ability to plug into other open source pools. I know that it's focused towards the whole Microsoft Suite so it's more geared towards the Team Foundation Server, but if they can add more support to pools, that would be great.

In terms of stability, it really works for us. There are drawbacks to every solution out there, it's built into it. Our company is stripped across using Visual Studio. Some of the architects use Visual Studio Code so they don't really need an extent of IDE. They have a nice cut of IDE using Visual Studio Code. In terms of stability, I don't think we have shifted away from Visual Studio at all. It will always remain our IDE tool of choice.

With Microservice Architecture it has become very easy for us to scale out. I think it's more about the way that we handle scale. The tool allows it. I would say the hardships comes with the planning for scale, as opposed to the actual tool accommodating itself. We have about 1500 users on Visual Studio and then we have a small team dedicated to the maintenance of the deployment. 

The technical team at Microsoft is known for their fast response time.

We utilized a bunch of templates for the initial setup instead of going through the trials and tribulations of setting up everything at once. 

I would highly recommend this solution. They've really gone the 9-mile to accommodate not only corporate or big companies, but small, single users to utilize the community issue or business vehicle, and to develop and build on application. I would highly recommend it to anyone. In the next version, I would like to see systems like Juta as well as more testing tools. There's a massive automation drive, anything in terms of more out of the box automation features for Selenium, or ACRONYM, or automation tools like that. I rate this program ten out of ten.

I use Visual Studio for one of my projects. I was designing programs and it helped me out making programs.

Microsoft Visual Studio could improve by being compatible with more operating systems. However, we understand the solution is proprietary to Microsoft.

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

Microsoft Visual Studio is stable and the performance was good. However, if you do not have decent hardware you will not have the same experience.

I have not used the support from Microsoft.

I would recommend this solution to others.

I rate Microsoft Visual Studio an eight out of ten.

Our primary use case of this solution is to develop and maintain the main programs of the company for which we work.

I really like the distributed software programming on the Windows platform and also we need to develop on this platform since the company's computers work with the Windows network. I like that I don't need any additional software to develop on this platform.

I haven't had any issues with the stability of this solution.

I believe the solution is scalable and we can increase our number of developers. We currently have 15 users. 

We don't really use technical support. Whenever we have an issue, we search on the internet for a solution. 

We used other solutions before, but we decided to switch to Microsoft Visual Studio because it is the best solution for developing the Windows platform. We considered using Delphi Solutions, but few people were familiar with the platform, so we chose Visual Studio. More people use Visual Studio.

The solution comes at a good price and, even though there are free versions out there on the market, I still prefer this product because I like its interface.

My advice to others is to simply install it and use it. I am really satisfied with this solution. My rating is eight out of ten. In the next version, I would like to see a better development tool. The current Mobile Application Development is very integrated.

I use this solution to develop desktop and web applications. I have it deployed on-premises.

The most valuable feature is the integration with different databases. There are many different databases that it supports.

The reporting services are quite limited in terms of features and need to be improved.

I would like to see installation and packaging features added to the next release of this solution.

This is a stable solution.

I have not needed to work with applications that needed scaling.

I think that it can handle many users, but we have between five and ten people using it.

The technical support by Microsoft is quite good.

We did not use another solution prior to this one.

The initial setup of this solution is straightforward. It was quite fast to deploy, measured in minutes. One person is enough for deployment and maintenance.

I installed the solution myself.

We did evaluate other options but choose this solution because it was more integrated with Windows.

For anybody who is implementing this solution, I would suggest checking the reporting services beforehand. They can create limitations.

Adding the installation and packaging features are really important and would improve the product a lot.

I would rate this solution an eight out of ten.

Profiling

Architecture (Code Map)

Test and Load Test

Collaboration grew through the implementation.

TFS - Agile (Scrum / Kanban)

IntelliSense

Better management of using clauses

Auto add/remove using reference

Auto detect / suggest References or Nuget Package

Six months (the 2017 version in particular).

NA

NA

NA

NA

NA

NA

Simple.

In-house.

NA

NA

We use the solution to check Azure codes and other things like ARM templates.

It has perfect integration into Microsoft. It goes straight to Azure, and it is massive. It can get very complicated, but because our customers use it, we need to work with them and discuss certain aspects of automation and security settings.

We recently started using this solution because specific customers found value in us having it. A particular customer uses the latest version, and we use it to automate the rollout of servers into Azure. We use it to specify that the scripts are working properly.

It is stable and running locally, so we didn't have any issues.

It's scalable. We are running it on a server, so it isn't in the cloud.

We are a Microsoft gold partner, but the technical support can be slow.

We currently also use GitHub.

The initial setup was very easy. After that, the deployment did not take a long time. For our test environment, it took a morning to enter everything, get the code and start working on it with the customer.

I rate this solution a nine out of ten.