Microsoft dropped a surprise announcement on developers of UWP apps. The company is transitioning support to the Windows App SDK for Windows 11 and, in a newly uploaded document, is encouraging UWP developers to migrate their own apps.
Microsoft first introduced Windows UWP in 2015 as a platform to develop apps for Windows 10. However, the company is now throwing its support behind SDK after releasing its latest OS, Windows 11, and demonstrates a proper migration strategy in its document.
For those wanting to hold out, there’s bad news. Windows developer Rafael Rivera stated in a recent tweet that Windows UWP will only get “bug, reliability and security fixes” from this point on. So despite any misgivings, it seems migration is the only real future for UWP apps — as Windows features don’t last very long once they hit this stage.
[Temporarily reviving my Twitter account]Microsoft just published documentation and guidance on migrating apps from “UWP” to [anything else].https://t.co/APJk1tSIn3This signals what I already told you before: UWP will only get “bug, reliability, and security fixes”.October 19, 2021
If you want to take the plunge, you’ll need to download the Windows App SDK Visual Studio extension (VSIX) installer first. Then either create a new project or migrate a previously existing app. If the latter, make sure to migrate by copying over asset files and not asset file contents.
Analysis: Why the switch?
We’ve been hearing the UWP death knell for a couple of years now, but the software and hardware giant breaks down in its own document why it decided to make the switch in the first place.
The biggest reason is that the Windows App SDK is backward compatible. The application works from Windows 11 all the way down to Windows 10, version 1809 (10.0; Build 17763), which is also known as the Windows 10 October 2018 update.
There are a host of other features that makes SDK a more appealing choice for developers, such as the use of the Windows UI 3 Library (WinUI 3), a more unified set of APIs and tools, .NET 5 compatibility, a more frequent release cadence that releases separately from Windows, an improved runtime environment (such as with the MSIX app container) and more.
It’s important to note that despite the overall flexibility in support, there are two notable cases for Windows Runtime APIs in which they’re not supported in desktop apps at all or run with restrictions: APIs that have dependencies on UI features that were designed for use only in UWP apps, and APIs that require package identity.
Go to Source