Uno Platform supports authoring apps using WinUI 3's API. This article details the changes required when migrating an application from the UWP API set to the WinUI 3 API set.
Read more about WinUI 3 and Uno Platform.
- NuGet updates:
Uno.UI
becomesUno.WinUI
Uno.UI.RemoteControl
becomesUno.WinUI.RemoteControl
Uno.UI.Lottie
becomesUno.WinUI.Lottie
Uno.UI.Foldable
becomesUno.WinUI.Foldable
- String replacements:
Windows.UI.Xaml
becomesMicrosoft.UI.Xaml
Windows.UI.Composition
becomesMicrosoft.UI.Composition
- Update
App.xaml.cs
:
MapControl
is missingMediaPlayerElement
is missingWebView
is nowWebView2
For a full list of unavailable controls and visual features, as well as timelines for restoration in some cases, consult the WinUI 3 Feature Roadmap.
Some WinRT APIs are unsupported in WinUI 3 Desktop apps, notably CoreDispatcher
, CoreWindow
, and ApplicationView
. Consult this guide for supported alternatives to those APIs. DispatcherQueue
, the replacement for CoreDispatcher
in WinUI 3, is supported by Uno Platform.
Instructions are available here for creating a new Uno Platform application targeting WinUI 3.