Microsoft Visual Studio Reviews

We use it for comprehensive support in software development, encompassing tasks such as code writing, unit testing, and deployment to both cloud and on-premises services.

It proved versatile for diverse purposes, serving as a valuable tool for developing solutions across web, desktop, and mobile platforms. It facilitated not only coding activities but also aided in managing repositories and deploying applications to various environments, whether they be cloud-based or on-premises infrastructure.

Within Visual Support, there are three versions available, each housed in distinct containers. I'm focusing on the Enterprise version due to its customizable nature. This version boasts additional features, such as a pricing application for enhanced functionality and comprehensive unit testing coverage. The testing capabilities extend to diverse features, providing a thorough examination of different aspects. Notably, the Enterprise version facilitates seamless integration with Microsoft products, leveraging the ease of connectivity within the Microsoft ecosystem. Moreover, it supports integration with open-source products, including Python, allowing for a flexible and inclusive approach to development.

When using Visual Support for web development, challenges arise when specific components require hardware configurations beyond the application's scope. Efforts are directed at enhancing the IDE and introducing features for seamless collaboration, extending to Azure with the Explore version. This version incorporates "live share," enabling real-time code collaboration among team members. Despite its advantages, challenges in diverse cloud environments may prompt the uninstallation of the application or entire development environment for resolution.

I have been working with it for approximately thirteen years.

The stability is noteworthy because Visual Studio offers both a release and a preview version. The release version is reliable, free of issues, and suitable for general use. However, for those seeking additional features and improvements, the preview version is available. This version allows users to test new features directly and report any issues to the community for resolution. While encountering some issues in the preview version, they are typically addressed promptly through community feedback, resulting in a stable and refined release version shortly thereafter. I would rate it eight out of ten.

High scalability makes it a strong recommendation, especially for enterprise-level development, given its robust capabilities as an integrated development environment. I would rate it ten out of ten.

I've interacted with Microsoft support, but the community support for Visual Studio testing has been particularly outstanding. Unlike conventional support, the community channels provide an open and collaborative environment, similar to open-source platforms. This allows users to easily report issues, open discussions, and communicate effectively, making it a gateway to a more responsive and interactive support experience.

Having used various products at different companies, I must highlight that Microsoft's development technology, particularly in the realm of databases, has proven to be more intuitive and superior. It demonstrated a higher level of user-friendliness and efficiency.

The initial setup is straightforward. Simply download the controller and proceed with the installation, selecting the desired options for a new environment and clicking through the prompts. I would rate it nine out of ten.

Setting it up in the initial stages used to be a time-consuming process, often taking more than an hour. This was primarily due to the need to download setup data, often distributed on CDs or DVDs, and then proceed with the installation. Additionally, a decade ago, machines were not as swift, further extending the setup time. However, in recent years, there's been a more efficient option. Users now have two options: an online installation and an offline installation. For the online version, users simply download it and direct it to the storage directory on their machines.

The pricing varies depending on the version, and with three options available (Community, Professional, and Enterprise), you can choose based on your needs. While the enterprise version can be relatively expensive due to its comprehensive features, I find the license I currently possess to be reasonable, considering it includes the full suite without additional activations or charges.

Overall, I would rat it ten 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.

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.

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.

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 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.

We use this solution to support a number of different web development processes across different tools and languages. 

This solution can integrate with almost any functionality offered by Microsoft.

We have been using this solution for three years. 

This is a stable solution. 

The initial setup is straightforward.

The pricing for licenses could be reduced to make this solution more competitive.

I would rate this solution an eight out of ten.