Modernizing .NET Applications
A Field Guide for Breathing New Life into Your Software
With .NET’s coupling to Windows environments, .NET apps haven’t had access to the bleeding edge of server automation or application deployment. Configuration management tools have only recently supported Windows in earnest.
Public clouds are now making a legitimate effort to woo .NET developers, but that wasn’t the case even five years ago. And many of the most exciting microservices patterns have been tougher to implement with the available .NET tools.
This situation has left you with some tough choices:
- Should you abandon .NET and do your new development in a more open source, Linux-centric language?
- Should you invest the bare minimum to keep existing .NET apps online but freeze new development?
A few years ago, that was a fair concern. However, with the introduction of .NET Core, the availability of new libraries, and some fresh architecture patterns, you have a viable path forward. You can confidently build new applications with .NET, while reengaging plans to upgrade the .NET apps you have.
About the Author:
Richard Seroter is a senior director of product for Pivotal.
He’s also an 11-time Microsoft MVP for cloud/integration, an instructor for Pluralsight, the lead InfoQ.com editor for cloud computing, and author of multiple books on application integration strategies. As a product director, he gets to lead product, partner, and customer marketing and help shape Pivotal’s position and messaging.
Pivotal Software, Inc.