Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
github avatar

Winui3 Migration Guide

  • 5.6k installs
  • 37.1k repo stars
  • Updated July 28, 2026
  • github/awesome-copilot

winui3-migration-guide is an agent skill for UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispa

About

UWP-to-WinUI 3 migration reference Maps legacy UWP APIs to correct Windows App SDK equivalents with before after code snippets Covers namespace changes threading CoreDispatcher to DispatcherQueue windowing CoreWindow to AppWindow dialogs pickers sharing printing background tasks and the most common Copilot code generation mistakes name winui3-migration-guide description UWP-to-WinUI 3 migration reference Maps legacy UWP APIs to correct Windows App SDK equivalents with before after code snippets Covers namespace changes threading CoreDispatcher to DispatcherQueue windowing CoreWindow to AppWindow dialogs pickers sharing printing background tasks and the most common Copilot code generation mistakes WinUI 3 Migration Guide Use this skill when migrating UWP apps to WinUI 3 Windows App SDK or when verifying that generated code uses correct WinUI 3 APIs instead of legacy UWP patterns Namespace Changes All Windows UI Xaml namespaces move to Microsoft UI Xaml UWP Namespace WinUI 3 Namespace Windows UI Xaml Microsoft UI Xaml Windows UI Xaml Controls Microsoft UI Xaml Controls Windows UI Xaml Media Microsoft UI Xaml Media Windows UI Xaml Input Microsoft UI Xaml

  • WinUI 3 Migration Guide
  • [ ] Replace all `Windows.UI.Xaml.*` using directives with `Microsoft.UI.Xaml.*`
  • [ ] Replace `Windows.UI.Colors` with `Microsoft.UI.Colors`
  • [ ] Replace `CoreDispatcher.RunAsync` with `DispatcherQueue.TryEnqueue`
  • [ ] Replace `Window.Current` with `App.MainWindow` static property

Winui3 Migration Guide by the numbers

  • 5,611 all-time installs (skills.sh)
  • +24 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #262 of 2,184 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

winui3-migration-guide capabilities & compatibility

Capabilities
winui 3 migration guide · [ ] replace all `windows.ui.xaml.*` using direct · [ ] replace `windows.ui.colors` with `microsoft. · [ ] replace `coredispatcher.runasync` with `disp · [ ] replace `window.current` with `app.mainwindo
Use cases
documentation
From the docs

What winui3-migration-guide says it does

--- name: winui3-migration-guide description: 'UWP-to-WinUI 3 migration reference.
SKILL.md
Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets.
SKILL.md
WinUI 3 uses standard STA without this protection.
SKILL.md
npx skills add https://github.com/github/awesome-copilot --skill winui3-migration-guide

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs5.6k
repo stars37.1k
Security audit3 / 3 scanners passed
Last updatedJuly 28, 2026
Repositorygithub/awesome-copilot

When should developers use winui3-migration-guide and what problem does it solve?

UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue)

Who is it for?

Developers working with winui3-migration-guide patterns described in the skill documentation.

Skip if: Skip when cached docs are empty or the task is outside the skill's documented scope.

When should I use this skill?

UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue)

What you get

Grounded guidance and workflows from SKILL.md for winui3-migration-guide.

  • Before-and-after migration snippets
  • Namespace and API mapping reference

By the numbers

  • Covers namespace, threading, windowing, dialogs, pickers, sharing, printing, and background-task migration areas

Files

SKILL.mdMarkdownGitHub ↗

WinUI 3 Migration Guide

Use this skill when migrating UWP apps to WinUI 3 / Windows App SDK, or when verifying that generated code uses correct WinUI 3 APIs instead of legacy UWP patterns.

---

Namespace Changes

All Windows.UI.Xaml.* namespaces move to Microsoft.UI.Xaml.*:

UWP NamespaceWinUI 3 Namespace
Windows.UI.XamlMicrosoft.UI.Xaml
Windows.UI.Xaml.ControlsMicrosoft.UI.Xaml.Controls
Windows.UI.Xaml.MediaMicrosoft.UI.Xaml.Media
Windows.UI.Xaml.InputMicrosoft.UI.Xaml.Input
Windows.UI.Xaml.DataMicrosoft.UI.Xaml.Data
Windows.UI.Xaml.NavigationMicrosoft.UI.Xaml.Navigation
Windows.UI.Xaml.ShapesMicrosoft.UI.Xaml.Shapes
Windows.UI.CompositionMicrosoft.UI.Composition
Windows.UI.InputMicrosoft.UI.Input
Windows.UI.ColorsMicrosoft.UI.Colors
Windows.UI.TextMicrosoft.UI.Text
Windows.UI.CoreMicrosoft.UI.Dispatching (for dispatcher)

---

Top 3 Most Common Copilot Mistakes

1. ContentDialog Without XamlRoot

// ❌ WRONG — Throws InvalidOperationException in WinUI 3
var dialog = new ContentDialog
{
    Title = "Error",
    Content = "Something went wrong.",
    CloseButtonText = "OK"
};
await dialog.ShowAsync();
// ✅ CORRECT — Set XamlRoot before showing
var dialog = new ContentDialog
{
    Title = "Error",
    Content = "Something went wrong.",
    CloseButtonText = "OK",
    XamlRoot = this.Content.XamlRoot  // Required in WinUI 3
};
await dialog.ShowAsync();

2. MessageDialog Instead of ContentDialog

// ❌ WRONG — UWP API, not available in WinUI 3 desktop
var dialog = new Windows.UI.Popups.MessageDialog("Are you sure?", "Confirm");
await dialog.ShowAsync();
// ✅ CORRECT — Use ContentDialog
var dialog = new ContentDialog
{
    Title = "Confirm",
    Content = "Are you sure?",
    PrimaryButtonText = "Yes",
    CloseButtonText = "No",
    XamlRoot = this.Content.XamlRoot
};
var result = await dialog.ShowAsync();
if (result == ContentDialogResult.Primary)
{
    // User confirmed
}

3. CoreDispatcher Instead of DispatcherQueue

// ❌ WRONG — CoreDispatcher does not exist in WinUI 3
await Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () =>
{
    StatusText.Text = "Done";
});
// ✅ CORRECT — Use DispatcherQueue
DispatcherQueue.TryEnqueue(() =>
{
    StatusText.Text = "Done";
});

// With priority:
DispatcherQueue.TryEnqueue(DispatcherQueuePriority.High, () =>
{
    ProgressBar.Value = 100;
});

---

Windowing Migration

Window Reference

// ❌ WRONG — Window.Current does not exist in WinUI 3
var currentWindow = Window.Current;
// ✅ CORRECT — Use a static property in App
public partial class App : Application
{
    public static Window MainWindow { get; private set; }

    protected override void OnLaunched(LaunchActivatedEventArgs args)
    {
        MainWindow = new MainWindow();
        MainWindow.Activate();
    }
}
// Access anywhere: App.MainWindow

Window Management

UWP APIWinUI 3 API
ApplicationView.TryResizeView()AppWindow.Resize()
AppWindow.TryCreateAsync()AppWindow.Create()
AppWindow.TryShowAsync()AppWindow.Show()
AppWindow.TryConsolidateAsync()AppWindow.Destroy()
AppWindow.RequestMoveXxx()AppWindow.Move()
AppWindow.GetPlacement()AppWindow.Position property
AppWindow.RequestPresentation()AppWindow.SetPresenter()

Title Bar

UWP APIWinUI 3 API
CoreApplicationViewTitleBarAppWindowTitleBar
CoreApplicationView.TitleBar.ExtendViewIntoTitleBarAppWindow.TitleBar.ExtendsContentIntoTitleBar

---

Dialogs and Pickers Migration

File/Folder Pickers

// ❌ WRONG — UWP style, no window handle
var picker = new FileOpenPicker();
picker.FileTypeFilter.Add(".txt");
var file = await picker.PickSingleFileAsync();
// ✅ CORRECT — Initialize with window handle
var picker = new FileOpenPicker();
var hwnd = WinRT.Interop.WindowNative.GetWindowHandle(App.MainWindow);
WinRT.Interop.InitializeWithWindow.Initialize(picker, hwnd);
picker.FileTypeFilter.Add(".txt");
var file = await picker.PickSingleFileAsync();

Threading Migration

UWP PatternWinUI 3 Equivalent
CoreDispatcher.RunAsync(priority, callback)DispatcherQueue.TryEnqueue(priority, callback)
Dispatcher.HasThreadAccessDispatcherQueue.HasThreadAccess
CoreDispatcher.ProcessEvents()No equivalent — restructure async code
CoreWindow.GetForCurrentThread()Not available — use DispatcherQueue.GetForCurrentThread()

Key difference: UWP uses ASTA (Application STA) with built-in reentrancy blocking. WinUI 3 uses standard STA without this protection. Watch for reentrancy issues when async code pumps messages.

---

Background Tasks Migration

// ❌ WRONG — UWP IBackgroundTask
public sealed class MyTask : IBackgroundTask
{
    public void Run(IBackgroundTaskInstance taskInstance) { }
}
// ✅ CORRECT — Windows App SDK AppLifecycle
using Microsoft.Windows.AppLifecycle;

// Register for activation
var args = AppInstance.GetCurrent().GetActivatedEventArgs();
if (args.Kind == ExtendedActivationKind.AppNotification)
{
    // Handle background activation
}

---

App Settings Migration

ScenarioPackaged AppUnpackaged App
Simple settingsApplicationData.Current.LocalSettingsJSON file in LocalApplicationData
Local file storageApplicationData.Current.LocalFolderEnvironment.GetFolderPath(SpecialFolder.LocalApplicationData)

---

GetForCurrentView() Replacements

All GetForCurrentView() patterns are unavailable in WinUI 3 desktop apps:

UWP APIWinUI 3 Replacement
UIViewSettings.GetForCurrentView()Use AppWindow properties
ApplicationView.GetForCurrentView()AppWindow.GetFromWindowId(windowId)
DisplayInformation.GetForCurrentView()Win32 GetDpiForWindow() or XamlRoot.RasterizationScale
CoreApplication.GetCurrentView()Not available — track windows manually
SystemNavigationManager.GetForCurrentView()Handle back navigation in NavigationView directly

---

Testing Migration

UWP unit test projects do not work with WinUI 3. You must migrate to the WinUI 3 test project templates.

UWPWinUI 3
Unit Test App (Universal Windows)Unit Test App (WinUI in Desktop)
Standard MSTest project with UWP typesMust use WinUI test app for Xaml runtime
[TestMethod] for all tests[TestMethod] for logic, [UITestMethod] for XAML/UI tests
Class Library (Universal Windows)Class Library (WinUI in Desktop)
// ✅ WinUI 3 unit test — use [UITestMethod] for any XAML interaction
[UITestMethod]
public void TestMyControl()
{
    var control = new MyLibrary.MyUserControl();
    Assert.AreEqual(expected, control.MyProperty);
}

Key: The [UITestMethod] attribute tells the test runner to execute the test on the XAML UI thread, which is required for instantiating any Microsoft.UI.Xaml type.

---

Migration Checklist

1. [ ] Replace all Windows.UI.Xaml.* using directives with Microsoft.UI.Xaml.* 2. [ ] Replace Windows.UI.Colors with Microsoft.UI.Colors 3. [ ] Replace CoreDispatcher.RunAsync with DispatcherQueue.TryEnqueue 4. [ ] Replace Window.Current with App.MainWindow static property 5. [ ] Add XamlRoot to all ContentDialog instances 6. [ ] Initialize all pickers with InitializeWithWindow.Initialize(picker, hwnd) 7. [ ] Replace MessageDialog with ContentDialog 8. [ ] Replace ApplicationView/CoreWindow with AppWindow 9. [ ] Replace CoreApplicationViewTitleBar with AppWindowTitleBar 10. [ ] Replace all GetForCurrentView() calls with AppWindow equivalents 11. [ ] Update interop for Share and Print managers 12. [ ] Replace IBackgroundTask with AppLifecycle activation 13. [ ] Update project file: TFM to net10.0-windows10.0.22621.0, add <UseWinUI>true</UseWinUI> 14. [ ] Migrate unit tests to Unit Test App (WinUI in Desktop) project; use [UITestMethod] for XAML tests 15. [ ] Test both packaged and unpackaged configurations

Related skills

How it compares

Pick winui3-migration-guide over generic C# skills when the task is specifically translating deprecated UWP APIs to WinUI 3 equivalents.

FAQ

What does winui3-migration-guide do?

UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue), windowing (CoreWin

When should I invoke winui3-migration-guide?

UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue), windowing (CoreWin

Where is the source documentation?

Ground claims in SKILL.md excerpts and linked reference files from the cached docs.

Is Winui3 Migration Guide safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.