Legacy WinForms applications face challenges with modern UI/UX expectations and finding developers, making modernization a critical consideration.
A hybrid approach is often more practical than a complete rewrite for large, complex applications, but it is not suitable for performance-critical software.
Hybrid WinForms and WPF applications present challenges like the airspace problem and differing threading models that require careful management.
The hybrid migration uses a WPF shell to host WinForms content, requiring a custom WindowsFormsHost to support MDI windows.
The starting point for the migration is a typical MDI-based WinForms application that includes third-party controls and modal dialogs.
The new WPF application is built to act as a modern shell, utilizing dependency injection and a dashboard for launching application features.
The WindowsFormsHost acts as a "black hole" in the WPF layout by parenting a native WinForms window handle (HWND) and requires separate STA threads for each UI stack.
Proper window destruction is critical in hybrid apps to prevent memory leaks, which involves carefully managing Dispose calls to avoid duplicates.
A custom WindowsFormsHost is created by inheriting from HWNDHost and implementing the core logic to build and parent the WinForms window handle.
An InteropManager class centralizes the logic for creating hosted windows and synchronizing properties like size, title, and border style from WinForms to WPF.
A dedicated connector project with callbacks and services acts as a bridge, allowing the WPF and WinForms applications to communicate without direct dependencies.
The complete legacy WinForms MDI application can be hosted inside the new WPF shell, preserving all its original functionality including third-party controls.
The MDI architecture enables a gradual migration by allowing individual child windows to be opened directly within the WPF shell, facilitating a step-by-step replacement.
Differences in keyboard behavior, such as tab navigation, can be resolved by implementing the IKeyboardInputSink interface within the custom WindowsFormsHost.
Hosted WinForms dialogs fail to close because the message loop is not processed, a problem solved by implementing a custom loop in the WindowsFormsHost to detect the close event.
The hybrid approach offers a viable path for modernizing large WinForms applications, and the complete source code for this demo is available on GitHub.
Jobs that call for the skills explored in this talk.