Azure DevOps vs. Microsoft Visual Studio

Azure DevOps works well when you’ve got larger delivery efforts with multiple teams and a lot of moving parts, and you need one place to plan work, track it properly, and see how everything links together. It’s especially useful when delivery and development are closely tied and you want backlog items, code and releases connected rather than spread across tools. Where it’s less of a fit is for small teams or simple pieces of work, as it can feel like more setup and process than you really need, and non-technical users often struggle with the interface. It also isn’t great if you want instant, easy programme-level views or a very visual planning experience without putting time into configuration.

Incentivized

When working with base C# code for desktop and web projects, then Microsoft Visual Studio is ideal as it provides the libraries and interfaces needed to quickly create, test and deploy solutions. It is when slightly more complex scenarios are required that issues can arise. The built-in integration for things like PowerBI Paginated Reports and dashboards is far from ideal.

Incentivized

• Utilize Git as a repository to share work between multiple users
• Ability to configure Pipelines to build containers to run virtual deployments and testing scripts.
• Split individual tasks and relate to master documents for quick navigation and ability to see overall picture of project.
• Track status of each task
• Integrate with Git to utilize branches, merging, approvals, history, etc.

Incentivized

• I like how the tabs and panels are organized; everything is gathered together so you can find what you're looking for quickly.
• If you can't find something, there's a thorough search engine that searches all of Visual Studio's features.
• The Team Foundation Server feature is fantastic since it allows us to easily deploy and roll back changes on the server.

• I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
• The wiki is not the prettiest thing to look at, so it could have refinements there.
• It could improve the search slightly better.

• Would be great if there was a better way to save and restore open tabs.
• The built-in test runner can be improved, for example, by adding the ability to save a set of commonly run tests, etc.
• Better integration for Microsoft SQL server would be great.

Incentivized

I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.

Incentivized

VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.

Incentivized

It's a great help to get more information about new feature release and stay updated on what the dev team is working on. I like how easy it is to just login and read through the work items. Each work item has basic details: Title, Description, Assigned to, State, Area (what it belongs to), and iteration (when it’s worked on). See image above.They move through different states (New → Discovery → Ready for Prod → etc.).

Incentivized

I love the overall usability of Microsoft Visual Studio. I’ve been using this IDE for more than 20 years, and I’ve seen it evolve by leaps and bounds. Today, with AI and code-suggestion/completion features, developers no longer need to remember countless libraries, methods, or language syntax, or invest a huge amount of programming effort to complete a project. It truly offers everything a developer needs to program, debug, test, and deploy in a single IDE.

Incentivized

When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.

Incentivized

There are many resources available supporting Visual Studio IDE. Microsoft whitepapers, forum posts, and online Visual Studio documentation. There are countless demonstration videos available, as well. If users are having issues, they can call Microsoft Support, but depending on the company's agreement with Microsoft, the number of included support calls will vary from organization to organization. I've found that Microsoft support calls can be hit or miss depending on who you get, but they can usually get you with the right support person for your issue.

Incentivized

IT is very complicated to understand all the functions that the environment has if you are not familiar with this type of development environments. It is important to select a good in-person training to achieve to understand all the possibilities and the capacity of the application. In this case, you will be able to develop a lot type of different applications.

Incentivized

If you are not accustomed to develop in this type of development environments it would be complicated to follow all the parts of the course because if the course does not include a great tour with all the concepts to develop you will not have the option to understand all the functions.

Incentivized

Was not part of the process.

Incentivized

Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.

Incentivized

I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.

• We have saved a ton of time not calculating metrics by hand.
• We no longer spend time writing out cards during planning, it goes straight to the board.
• We no longer track separate documents to track overall department goals. We were able to create customized icons at the department level that lets us track each team's progress against our dept goals.

Incentivized

• Using the integration between Visual Studio and our source control service, the cost of re-work and losing code is drastically reduced.
• Paid versions of Visual Studio enable developers to be so much more productive than hacked-together open source solutions that it's hard to imagine developing in Windows without it.
• When combined with support subscriptions and the vast array of free online help options available, Visual Studio saves our developers time by keeping them coding and testing, not wasting their time trying to guess their way out of problems or spend endless hours online hoping to find answers.

Incentivized