What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
Buyer's Guide
Microsoft Visual Studio
April 2024
Learn what your peers think about Microsoft Visual Studio. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
768,415 professionals have used our research since 2012.
For how long have I used the solution?
I've been using Microsoft Visual Studio since the early versions of VB6, which is like in 2006 or 2005.
What do I think about the stability of the solution?
The stability is great. There aren't bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How was the initial setup?
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.
What about the implementation team?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.