
Recent UWP & .NET 5, .NET 6 News and Uno Platform Plans
You might have caught the news that Microsoft will not invest in moving UWP to .NET5/6. Naturally this raised questions about how Uno Platform is affected, especially as Uno Platform also ships in lockstep with .NET. The short answer is – this news does not change anything for our users as Uno Platform has been architected to support both UWP as well as WinUI 2.x / 3. We intend to continue this support for as long as these are supported platforms at Microsoft as it is straightforward and automatic for us to support both. For the long answer – the important part is to understand what UWP is. UWP is a combination of an app model with isolation (the sandbox) and APIs (WinUI+WinRT). Uno Platform has been all about implementing the APIs, while leaving the app model to the underlying platform. If you’re running an Uno Platform app on iOS, Android or the Web with WebAssembly, the app will need to play along with the sandbox that the system provides. Uno supports both the Windows.UI.Xaml (a.k.a WUX, bundled with UWP) and Microsoft.UI.Xaml (a.k.a MUX available in WinUI 2.x and WinUI 3/WinAppSDK). Uno provides support for those through the Uno.UI.* and Uno.WinUI.* NuGet packages respectively, and are built from the same source code. If you’d like to move from WUX (UWP) to MUX (WinUI 3), and also want to take advantage of