Why WinForms must not change - yet reinvented itself with .NET 11!
Presented by dotnet, this session examines why preserving WinForms compatibility is essential for long-lived business applications, and how .NET 11 supports modernization without a wholesale rewrite.
Compatibility as a modernization strategy
Many WinForms line-of-business applications contain decades of domain knowledge, customer-specific workflows, and millions of lines of proven code. Rewriting them is rarely economical, while breaking behavioral or designer compatibility can put that investment at risk.
The session frames WinForms modernization around preserving those foundations while allowing applications to evolve. Rather than imposing a new UI model, the approach is to introduce deliberate boundaries between existing business logic and the parts of an application that can be updated or replaced.
Visual and accessibility improvements in .NET 11
A new opt-in visual-styles generation gives controls modern metrics and appearance while preserving compatibility by default. Applications can adopt updated presentation deliberately, rather than having it imposed on existing interfaces.
The session covers:
- Toggle switches.
- Flash-reduced form startup.
- Live Windows visual and accessibility settings.
- Improved focus and text-scale handling.
- Smoother batched UI updates.
- New presentation capabilities.
These changes support current Windows design conventions and accessibility expectations while retaining the compatibility required by established applications.
Architectural boundaries for safer modernization
The modernization approach separates concerns that are often intertwined in existing WinForms applications:
- Generated designer state from application logic, making the distinction between designer-managed code and application behavior explicit.
- Fixed layouts from adaptive layouts, allowing presentation to evolve without treating every existing layout as disposable.
- Synchronous UI mutation from responsive workflows, creating room for more responsive application behavior.
- Irreplaceable business rules from replaceable presentation and infrastructure, preserving domain knowledge while updating surrounding components.
These boundaries provide structure for incremental changes without discarding the application's existing value.
AI-assisted development and intelligent workflows
The session distinguishes two roles for AI in WinForms modernization.
First, AI-supported development needs enough structure from the designer and runtime to understand a form, preserve its intent, and transform it safely. The architectural boundaries described above are intended to make that work practical at a scale that would be difficult to achieve manually.
Second, applications need runtime foundations for adding AI-powered functionality, including:
- Domain-specific copilots.
- Intelligent workflows.
- Local or connected AI services.
The goal is to add these capabilities without rebuilding the entire product. Compatibility remains the baseline, while presentation, responsiveness, accessibility, and AI integration become areas for deliberate, incremental improvement.