Microsoft Visual Studio Reviews

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.

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.

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.

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.

Right now I'm primarily using the solution for C-Sharp development.

I've actually been using the solution on iOS to do Xamarin apps. That might be something that's quite atypical, in terms of using the solution. It's not easy to do.

Having also done development within a text, I really enjoyed the (what I believe is called) IntelliSense feature. It helps if you are doing development within a text browser.

The integrated debugger is fantastic. 

None of these are particularly new features. Everybody else has been using it for 20 years too.

I find it funny that a lot of people complain about the solution. However, I find that it provides users with so many great and useful features, like console output, for example. You always have the option to dump a whole bunch of items out if you don't need them in the production.

While you're coding, it's really nice to be able to print stuff out and make sure that all the data is being organized the way you want it to be. 

It's got a lot of tools integrated into it. 

There's a community edition that is absolutely free to use. It's pretty good.

If you use the professional edition, you can do unit testing much easier. You can do mock-ups and tasks of that nature. It would be nice if they made that available on the community edition as well. 

There needs to be a feature upgrade, especially for the free features. They might have done so in the past or over the last few years. Still, it would be nice it if happened more often.

During some research into the product, I've discovered that they are trying to apply AI, as well as machine learning. This would be a welcome edition. They will most likely be advanced features. That means they won't be free. However, maybe in the future, they will be, given that enough time passes.

Technical support needs to be improved. Right now, it's not great.

I've used the solution for a long time. I would estimate I've used it on and off for 20 years. 

The solution is actually really stable. It's been around for so long. It's not like Microsoft Office products where a few years ago they decided to go redesign everything, and then the file formats were no longer compatible. In that case, users were confused as to which excel format to save in. This solution has been the same for 20 or so years. The format is the same. It hasn't changed. It remains very stable. 

I can't really comment on that aspect of the solution. I work on small projects, so I've never used it on any kind of scale.

There are about 20 people who use it in our organization. They're either software developers or software testers.

I haven't actually used their formal tech support, but have tried using their Microsoft answers. A lot of them are out of date. They're terrible. The support is basically: "Well, we can't reproduce that."

They don't even seem to do a search for themselves on Stack Overflow. You basically Google search to see if somebody else has answered the question. I would say that of course, it is free, so you get what you pay for and therefore the bar should be low on expectations. Still, it can be frustrating.

I have considered that maybe they have some poor interns trying to answer these questions, and they certainly don't seem too interested in providing the type of detailed responses a user might require. That's just what my impression is from trying to find answers occasionally. 

The nice thing about their model is if somebody asks a question, people will answer it. Then everyone can vote on the answer as the solution, and people can follow up. 

On Microsoft, if you go to their forums or help section for the product, you'll see the question is five years old. Nobody will ever say whether the answer they gave was the solution helped. So users often get confused. You need to ask yourself: "Do I spend half an hour deploying this? Or do I keep Googling?" It's awful.

The initial setup is really easy. You just download it and start it up.

I don't think my company uses much of an implementation strategy. There aren't as many protocols or structures. If we need it, we just download it and begin using it. 

I would say the only downside with this setup is that although it's usually pretty clear what libraries you want to include, it is slow to download. You do have to set aside a time when you can start the download. It's best to go off and do something on your own. You'd hate to do it at work, as you'll have to wait and you'll have nothing else to do. It's going to take half an hour to download at least.

Maintenance requirements are extremely low. There's next to none, really. 

The solution has a community version, which is free. It also has a paid version, with a few more premium features, but the free version is still really useful.

I believe I am using the 2015 version of the solution. It's the default for C-Sharp programs at the very least. Depending on what programs we get in, we can often use it extensively. I don't have plans to expand the solution right now. There are other solutions that would be available to us. 

For example, if we're going to do Python development, we'll probably use PyCharm instead of Visual Studio. Visual Studio does support Python, but PyCharm was in there before and everybody knows it. So we don't really force people to use it. Our company is a small company, where developers can choose their own development avenues.

In terms of advice, I would give to other users, I would suggest following a tutorial at first if you've never used it. They actually have some good tutorials online. If you actually follow them line by line, you get the setup and training that you need. Their help answers to random user questions are terrible, however.

I'd rate the solution eight out of ten, mostly due to the fact that it's got a lot of features. If you want to do development, it makes it easy. I know, on the other hand, that there are some other really amazing tools out there. However, they aren't necessarily free. It's a good selling point: you get all this stuff for free, it's standard, and lots of people use it. Once you've learned it, it's quite useful.

My main use case for Microsoft Visual Studio is prototyping different products, different features, and functionality. For example, I have used Microsoft Visual Studio for prototyping by creating a database layer to some app builder. I do not work on other types of projects or features with it.

The best features Microsoft Visual Studio offers are its relatively easy usability and pretty good debugging features.

When I mention the debugging features, a particular function within Microsoft Visual Studio's debugger that stands out to me is how you can attach to running processes, stop the code, and see what's happening, including the status of variables and other information.

Microsoft Visual Studio has positively impacted my organization by providing a standardized interface, making it easy to collaborate across teams. It's easy to help other people out or get help because everybody knows it. Having that standardization has indeed led to measurable improvements; it makes onboarding fast because it's somewhat of a standard that everybody knows. So it's easy for everybody to get into it and start working.

I think Microsoft Visual Studio can be improved because sometimes the setup can be a little bit complicated and it seems sometimes a little bit bloated, with a large download for what it is. There is nothing about performance, usability, or updates that needs to be discussed.

I have been using Microsoft Visual Studio for over ten plus years.

Microsoft Visual Studio is stable.

From my perspective, I cannot really answer about Microsoft Visual Studio's scalability because I only run one instance, but it seems to be scaling fine if the entire company is using it.

I have never used customer support for Microsoft Visual Studio; I always just go online and search if I have any questions.

I did not previously use a different solution before Microsoft Visual Studio; we kind of always used that.

From my side, Microsoft Visual Studio certainly saves time because I know it, so it's easier for me to use; from a company perspective, I cannot really know the metrics.

I do not really handle pricing, setup cost, and licensing because that is managed through the corporate; I'm not dealing with this. For private use, the free version worked pretty well when I used it, although it was missing some vital features.

Before choosing Microsoft Visual Studio, we did not evaluate other options; we always use Microsoft Visual Studio.

My advice to others looking into using Microsoft Visual Studio is to know that there's a lot of information about it out on the internet, so if you run into any issues, you can easily look it up. I gave this review a rating of eight out of ten.

You can use the solution to do coding and drag and drop. It is easy to install with web documentation. 

Microsoft Visual Studio needs to improve integration. 

I have been using the product for 15 years. 

Microsoft Visual Studio is stable. 

The solution is scalable. 

The tool's deployment is straightforward. Deployment takes between ten minutes to one day. One resource is enough to handle the deployment. 

Microsoft Visual Studio is not expensive. Its licensing costs are expensive. 

I rate the product a nine out of ten. 

We use Microsoft Visual Studio for general development, web development, and IT development.

Microsoft Visual Studio is an easy-to-use solution. All recent versions of Microsoft Visual Studio have live code, which allows multiple people to code on the same thing. The other valuable features of Microsoft Visual Studio are the integrations and extensions.

The solution’s technical support could be improved.

I have been using Microsoft Visual Studio for more than ten years.

I rate Microsoft Visual Studio ten out of ten for stability.

Over 1,000 users are using the solution in our organization.

I rate Microsoft Visual Studio a nine out of ten for scalability.

The solution's technical support is average. In some cases, I find it very good, and in other cases not so good.

The solution's initial setup takes a while but is quite straightforward.

We purchased an expensive enterprise version of Microsoft Visual Studio.

Microsoft Visual Studio helps streamline team collaboration. I would recommend Microsoft Visual Studio to other users.

Overall, I rate Microsoft Visual Studio a nine out of ten.