ASP.NET vs. Azure DevOps vs. JetBrains Rider

Well suited: for interfaces between machines data and applications. Made as a service. For web applications in factories where you don't have access to thick clients due to the environment. not well suited: quick measurements and fast data transitions between different applications. When time dependency is needed, then you better can choose other solutions.

Incentivized

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

Initially you may think it’s not worth paying and that there are better free options, which is definitely a lie we once tried to live with. It has everything you may ever need in .NET world, code analysis and debugging works super well and all the SQL/noSQL related integrations are just next level compared to the competition. It’s worth every penny.

Incentivized

• It has a great documentation so new or experienced, you appreciate quick access to quality information
• It’s very fast, uses less memory than initially expected that has decreased our costs after moving from python
• It speaks the language of the design patterns really well, so our backend apps are written fast together and connect to frontend systems flawlessly

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

• Provides a smooth, efficient IDE for developing .NET applications. Performance has been much better than Visual Studio in my experience.
• Integrated refactoring tools are really comprehensive and useful.
• Integrates with other JetBrains products such as TeamCity, Upsource, dotTrace, etc.

Incentivized

• Net is just like plug and play, we have to focus on a logic of code rest part can be handled by ASP. Net framework.
• It's a best for only web development.
• One downside with ASP.NET is its reliance on the .NET framework.

Incentivized

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

• Startup time. It takes a while to index big projects.
• Rarely it loses the intellisense and the only way to get it back is by restarting.
• Memory usage for big projects

Incentivized

It is the backbone of all our products

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

Due to the performance and productivity benefits we get with Rider, we will continue to use it for the foreseeable future.

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

Rider is a great IDE with extensive C# refactoring support and .NET-specific knowledge. This is great for building .NET applications but for our purposes, the Unity specific suggestions are really helpful.

JetBrains Rider is great as an editing and debugging environment. It reliably connects to the Unity editor and allows debugging, which some IDEs are not as reliable at doing.

Incentivized

Very good, depending on the requirement and budget.

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

The support forums and knowledge base are extensive and the JetBrains support staff respond quickly to new posts and help resolve issues. There is also a publicly accessible issue tracking system, which allows you to stay on top of any bug fixes or enhancement requests.

Incentivized

Was not part of the process.

Incentivized

We choose ASP.NET because our core business is working with the SAP HANA database using SAP Business One. We can develop state-of-the-art applications with Razor and Visual Studio 2022 fast and with excellent application performance response. Working SAP Hana with JAVA could be more challenging because it has fewer developers communities, and it could be harder to find a solution for a question.

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

Rider is hands down smoother and way less glitchy than Visual Studio Enterprise. There are way more refactoring capabilities and spell check so that your code is readable, maintainable, and easy to follow. Since Rider is cross-platform, our developers are no longer constrained to only using Windows. We can now get a familiar development environment across Mac, Windows, or Linux!

Incentivized

• We realized positive returns due to interns and new employees already having experience due to the free academic versions available.
• Being able to evaluate the express version prior to purchase was helpful.
• Performance is adequate, but not as responsive as C++. I guess the trade-off is ease of use and being able to find qualified personnel.

Incentivized

• 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

• Built in Resharper into the license fee, great, you likely want it
• Demands less resources from computer so needing a beefy work computer might not be the case, save money on equipment.

Incentivized