Microsoft Visual Studio Reviews

I use the Visual Studio Team System for programming. 

My company works with outsourced programmers. The solution helps us to test, integrate and foresee the code quality. We can trace the development stages. 

I like Azure DevOps integration and the nativeness of the C#. 

Visual Studio Team System needs to improve documentation. 

I have been using the solution for ten years. 

I rate the solution's stability a nine out of ten. 

I rate the product's scalability a nine out of ten. 

Visual Studio Team System is expensive, but it is worth the money. 

You can start using the community edition first. I rate the tool an eight out of ten. 

It's up to the client or the software we are using. I use VB .NET or C# sometimes.

You can get two tables, child and parents tables, and you can handle tasks such as invoicing, receipts, et cetera. I like to have the results on hand fast. It's making my life easy. 

Many firms can use it. It's pretty prevalent. 

I like the copy-paste all capabilities.

The stability is okay.

You can expand usage if you would like to. 

I had to use VB .NET in place of using C# immediately with the child and parent table.

Generally, the solution works well and I haven't really had issues with it. 

We'd like the solution to be more secure. 

The installation can take a long time. 

We'd like the solution to be more stable. 

Technical support does not respond quickly.

The ability to scale can be difficult.

I've been using the solution for 15 years. 

The solution is mostly stable. It's rate it six or seven out of ten. It could be better.

The solution can scale, however, it's not straightforward. Sometimes it's very confusing in terms of what you need to do to make it happen. 

We have three users on the solution right now. 

We do plan to increase usage in the future. 

We are in Lebanon and we had to wait for Microsoft to reply to us. We used it two years ago, however, and they were responding fairly well. 

They could be faster. 

I started with VB Access and Visual FoxPro. 

The initial setup is pretty hard to set up. 

It took too long to install it. We also needed the new hard discs. It's very big. It's not a light application. It's about 25GBs. 

The deployment took about two hours. 

We handled the installation ourselves without ht need of integrators or consultants. 

I can't speak to the exact cost of the solution. It's not an aspect that I deal with. 

I'd recommend the solution to others. 

I'd rate the solution eight 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.

We use the solution to develop applications. 

Microsoft Visual Studio needs to improve integration. 

I have been using the product for five years. 

I rate Microsoft Visual Studio's stability a nine out of ten. 

The tool's deployment is straightforward. It takes less than an hour to complete. 

I can install the solution by myself. 

Microsoft Visual Studio is a free product. 

I rate Microsoft Visual Studio a nine out of ten. 

I think Microsoft Visual Studio is a good tool.

I think it is very successful and easy to use. I currently do not see any areas to develop. Microsoft Visual Studio is an excellent product.

The stability is fine.

We have a very scalable solution with Microsoft Visual Studio.

We have not had the need to use technical support, but the website has been good.

The initial setup could be more straightforward. After the initial setup, it is easy to use and develop codes in different languages.

A license is required. I think it is a good product, but the price is high. They could sell it at a better price point.

I would rate Microsoft Visual Studio a nine out of ten.

We use it basically for just coding. 

It's great for personal use. 

The extensions are valuable. I was able to download the extensions that were important to me. For example, I can use the solution to highlight syntax on the code or change the theme of Visual Studio. Or, if I'm working on PHP, I can download the PHP extension. If it's Python, I can download Python extensions. Et cetera. It's flexible and gives you options. 

The solution can scale. The solution is also very stable. 

It's updated regularly. 

The cost is reasonable, and they do have a free option.

I can't speak to any necessary improvements. It does what I need it to do. 

I'd like the product to become more secure. You could potentially, for example, download an extension that contains malware. 

I've used the solution over the past three or four years. 

The solution is stable. It has regular updates. There are no bugs or glitches. It doesn't crash. 

The solution is able to scale. 

I basically use the solution myself for my purposes. 

I didn't really use tech support so much. I wouldn't know much about it.

I did not previously use a different product. 

You just download the solution and have it running on your system. Therefore, the setup is pretty straightforward. It only takes a few minutes to get everything up and running. 

The implementation can be done in-house. We didn't need any integrators or consultants to assist us. 

There is a free version of the solution, which I 've used. I'd rate the cost of the solution overall eight out of ten. It's pretty reasonable. 

I would recommend the product to others. It supports different types of software development for websites, web apps, mobile apps, computer programs, or any other web services.

I'd rate it eight out of ten. 

We use the Microsoft Visual Studio environment to write code for applications.

The most valuable features of Microsoft Visual Studio are the way we are able to design code, deploy, and test our application. It is easy to move an artifact from the start to the deployment stage. It has well-defined processes that you can integrate with any team. Additionally, the solution is always improving.

Microsoft Visual Studio can improve by bringing back designers. They used to have designers for architecture charts and diagrams. They were able to do things, such as database design. If they can bring them back, it would be great.

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

Microsoft Visual Studio is stable.

Microsoft Visual Studio can scale in terms of expected loads. It is highly scalable.

We have four people who use the solution in my organization.

We were using another solution prior to Microsoft Visual Studio.

Microsoft Visual Studio's initial setup is easy. The process took approximately two to three hours.

We did the implementation of Microsoft Visual Studio in-house. We use one person for the deployment and support of the solution.

We have seen a return on investment using Microsoft Visual Studio. Within a week you can be more proficient and see the value.

You have to be a subscriber with a Visual Studio subscription to use the solution and the organization has to purchase a license that's linked to the account.

My advice to others is they should try Microsoft Visual Studio. They will achieve quicker results in terms of being able to deliver the project compared to the competition.

I rate Microsoft Visual Studio a ten out of ten.