Unifying Desktop Experience with UWP

Introduction

Many enterprises still rely on mature Win32 and WPF applications but want to take advantage of the modern UI capabilities offered by UWP and WinUI 3. This discussion outlines key patterns, tools, and pitfalls when attempting to merge these worlds.

Key Benefits

• Consistent theming and Fluent Design across all components.
• Access to newer Windows APIs (e.g., notifications, biometric authentication).
• Improved performance with XAML Islands and the Windows App SDK.

Approaches

1. XAML Islands: Host UWP/WinUI controls inside existing Win32/WPF windows.
2. Desktop Bridge: Package legacy apps as MSIX and augment with UWP APIs.
3. Hybrid Projects: Use the Windows App SDK to build a mixed codebase.

Sample Code

using Microsoft.UI.Xaml.Controls;

// In a WPF window:
public partial class MainWindow : Window
{
    public MainWindow()
    {
        InitializeComponent();

        var uiElement = new WinUI3Control();
        var island = new WindowsXamlHost();
        island.Child = uiElement;
        this.Content = island;
    }
}

Common Challenges

While XAML Islands provide a straightforward path, developers may encounter threading issues, DPI scaling inconsistencies, and resource management complexities. The Desktop Bridge can simplify distribution but requires careful handling of app capabilities and manifest declarations.

Resources

• XAML Islands documentation
• Desktop Bridge guide
• Windows App SDK on GitHub

Discussion

Feel free to share your experiences, ask questions, or suggest alternative approaches.