Content

Many .NET teams have been working for years on stable but historically grown WinForms or WPF applications. Over time, typical problems arise: technical debt, outdated third-party components without support, missing tests, hard-to-maintain structures, and a UI that no longer feels modern. At the same time, hundreds of open bugs and the loss of key knowledge holders tie up development capacity. Innovation falls behind while customers and management continuously demand more features and faster development. In this talk, I will show the different paths to modernization, from complete redevelopment to gradual evolution, and when each approach makes sense. Using concrete examples, we will discuss how teams can make their applications future-proof despite technical debt and resource constraints.