Is your Blazor codebase slowly becoming unmaintainable due to "death by a thousand bad decisions"?

The ease of Blazor often tempts developers to put too much logic in Razor components, leading to massive files and tightly coupled code that becomes impossible to test or upgrade. As we look toward the future of .NET, sticking to these legacy habits prevents you from leveraging the modularity and performance benefits of modern web architecture.​

This talk moves beyond simple bug fixes to explore the architectural choices that determine an application's long-term success. We will cover:
- Identifying common mistakes when building Blazor applications
- Architectural patterns for creating clean and testable UI components.
- Quick fixes to big mistakes that yield immediate results.
- Techniques to refactor complex components into maintainable code.
- How to write future-proof code that evolves with the .NET ecosystem.

Avoiding these mistakes leads to codebases that are easier to read, faster to test, and simpler to upgrade. You will move from "making it work" to "engineering it right," ensuring your application is ready for the future.