I use it just for coding our applications and features. We are using version 4.5, which is an old version. We haven't tried its latest version.
It probably is deployed in a private cloud. It is a part of our firm architecture or infrastructure.
I use it just for coding our applications and features. We are using version 4.5, which is an old version. We haven't tried its latest version.
It probably is deployed in a private cloud. It is a part of our firm architecture or infrastructure.
It is a very common and strong product. A lot of support is available for this product.
It needs more integration with other tools for monitoring. Microsoft also needs to make it more modern to make it work with microservices and the cloud. It is a bit outdated currently.
I have been using this solution for five years.
It is stable. We didn't find any issues.
I don't know much about scalability. It is more related to the infrastructure side.
We have around 2,015 people in our organization who use this solution.
I have never really used Microsoft technical support. I just find the information on the internet.
It is easy to set up. The deployment duration depends on the projects. We are working with different projects and persons. For one of our projects, we need one week to deploy. We usually test when all the teams have integrated changes in an environment. It takes some time to test. After that, the changes are deployed to another pre-production environment, where we again test. After that, when we are sure, we deploy to the production environment.
It is an old technology, and I would like to try using a new technology. However, it is necessary for us to stay with this technology because we have a legacy product, but we are thinking of updating to newer versions or migrating to another technology. We didn't do that in the past because of the fear of losing some of the features and having any kind of breakage because of incompatibility. We are looking for microservices for the database. I would advise not to keep a lot of gap between upgrades. The risks are more when you upgrade after a long gap, such as four years. It also takes more time to test all the functionalities.
I would rate Visual Studio Test Professional a seven out of ten.
As a software developer working on the Microsoft platform, I find Visual Studio Test Professional to be a valuable tool for ensuring the quality and reliability of my applications.
Visual Studio Test Pro is super helpful for my Microsoft app work. It easily works with Visual Studio, helping me find and fix bugs fast. It does both manual and automated testing, making sure my app works well.
In terms of improvement, I would appreciate some enhancements in the interface, maybe adding more color options.
.
Visual Studio Test Pro is quite stable.
It is fairly scalable.
The support is good, but it could be a bit faster.
The initial setup is fairly simple.
It is a bit pricey.
Overall, I would rate Visual Studio Test Pro as an eight out of ten.
We use this solution to develop code.
The price could be improved.
I have been using this solution for two years.
I would rate the stability a ten out of ten.
I would rate the scalability a ten out of ten.
The initial setup is easy. It's easy to configure.
The deployment can be done in-house.
We pay for the license. The licensing model is per year. So, yearly-based license.
I would rate the pricing an eight out of ten, where ten is the most expensive and one is the cheapest.
Overall, I would rate the solution a ten out of ten. I would definitely recommend using the solution.
Visual Studio is an IDE that we use for development.
Visual Studio is the easiest to use.
We have used Visual Studio for as long as I can remember. It has been about 10 years.
I rate Visual Studio nine out of 10 for stability.
I rate Visual Studio nine out of 10 for scalability.
Setting up Visual Studio is straightforward, and it takes a couple of hours at most.
They have different pricing levels. There is a free community edition, professional, etc. It depends on the use. The price is reasonable, but it's not the best.
I rate Visual Studio Test Professional nine out of 10. I highly recommend Visual Studio for any software engineer.
It's great for the development of .NET.
The solution should be cheaper. But unfortunately, Microsoft products are usually expensive.
We've been using this solution for several years and have used Visual Studio 10, 12 and 13. We use it both as a cloud solution and on-premises.
It is a stable solution.
It is a scalable solution. It is secure because most of our applications are in .NET.
The deployment was not complicated, and our developers completed the deployment. Only those two developers use the solution, and we don't plan to increase usage at this time.
Visual Studio Test Professional has an annual license.
I rate this solution a ten out of ten. I recommend Visual Studio Test Professional, primarily if you work with .NET. If we are developing something in .NET or C++, we use Visual Studio. But if we are developing something in Java, we have to use Java.
Visual Studio is for custom software development.
Visual Studio is highly powerful. It's probably the best software development tool on the market.
Some of the features appreciated by our teams that work with VS are:
IntelliSense, rename functions (classes, methods, variables), move definition to file, error navigation, search in files (match case, regex), NuGet package manager, GIT experience (especially at solving merge conflicts and view history on a specific file, compare with the previous file to see changes in time), watch list and the fact it can be pinned for the variable you are monitoring, conditional breakpoints, moving execution line up when debugging, shortcuts to arrange elements in the page and remove unused namespaces, possibility to chose the Thread you want to monitor when you have multiple threads, code snippets, easy navigation to the definition and to other classes/methods/properties that refer them, and configuration of code cleanup on multiple profiles and with a lot of options.
We have been selling Visual Studio for more than 10 years.
Sometimes Visual Studio is slow. It uses a lot of resources like memory and processing power. You should optimize the performance by only installing what you need on your machine. Don't install unnecessary things that will slow your machine.
It depends on what you mean by scalability. Only one person uses Visual Studio at a time, but it's scalable in terms of project size. We have
70 users. We will grow usage as we grow the department and the company. We're expecting between 5 and 10 percent growth in usage next year.
Microsoft support could be faster. It took a while to get to a knowledgeable person in some cases, but we got the answer that we were looking for in the end.
Setting up Visual Studio is straightforward. Each developer configures their own environment.
We have both options. Some licenses are paid yearly. Others are monthly subscriptions.
I rate Visual Studio Test Professional nine out of 10.
Our primary use case of this solution is for UA automation. I'm a process manager and we are customers of Visual Studio.
The product is very easy to use and we were able to scale up the automation solution quickly which was beneficial.
It's an expensive solution which is an issue for us.
I've been using this solution for five years.
The solution is stable and we get upgrades every couple of years. Most of our developers use Visual Studio; we have around 150 users in total.
The initial setup is straightforward, it took us around four to five hours and we were able to do it by ourselves with our own three-person IT team.
We pay an annual licensing fee.
We took a look at Tricentis Tosca and SmartBear TestComplete a few months ago but nothing has been finalized. We're looking for an alternative to Visual Studio Test Professional.
If cost is not an issue then I would recommend this solution.
I rate this solution eight out of 10.
Visual Studio Test Professional is purely used for the development of web applications, Windows services, and API.
Visual Studio Test Professional is a complete IDE. The most valuable features of Visual Studio Test Professional are the IntelliSense and the ease of adding the NuGet packages.
Sometimes, the solution hangs, so its performance could be improved.
I have worked for different organizations and have been using Visual Studio Test Professional since 2010.
Visual Studio Test Professional is a stable solution.
Around 50 users are using Visual Studio Test Professional in our organization.
The solution's technical support is good, and we have no complaints.
The solution's initial setup is straightforward for me because I have been using it for quite some time.
We implemented the solution through an in-house team.
We have seen a return on investment with Visual Studio Test Professional because it improves developers' efficiency.
Our company pays a yearly licensing fee for Visual Studio Test Professional.
I would recommend Visual Studio Test Professional to other users.
Overall, I rate Visual Studio Test Professional a nine out of ten.