Windows App SDK 1.0.0-Experimental with WinUI 3, no longer released

Microsoft has just released Windows App SDK 1.0.0-experimental, a toolkit that enables desktop app developers to build apps with a modern Windows user interface, APIs, and platform features.

SDK version 1.0.0 brings the following features and improvements:

WinUI 3

This version of WinUI 3 focuses on building new features for stable version 1.0 and fixing bugs.

  • New features: Support for displaying a ContentDialog per window rather than per thread.
  • Bugs: For the full list of bugs fixed in this release, see the GitHub repository.
  • Samples: To see WinUI 3 commands and features in action, you can clone and create the WinUI 3 Command Gallery app from GitHub, or download the app from the Microsoft Store.

Push notifications (experimental function)

This release introduces a push notifications API that can be used by MSIX packaged desktop apps with identities based on Azure App Registration. To use this feature, you need to sign up for Microsoft’s private preview.

Important limitations:

  • Push notifications are only supported in MSIX packaged apps that run on Windows 10 version 2004 (build 19041) or later.
  • Microsoft reserves the right to disable or revoke apps from push notifications during private preview.
  • Microsoft does not guarantee the reliability or latency of push notifications.
  • During the private preview, the volume of push notifications is limited to 1 million per month.

Windowing (experimental function)

This release includes updates to the Windowing APIs. This is a set of high-level windowing APIs, centered around the AppWindow class, which enables easy-to-use windowing scenarios that integrate well with the Windows user experience and other applications. . This is similar, but not the same, to UWP AppWindow.

Important limitations:

  • This output of AppWindow is currently only available for Win32 applications (both packaged and unpackaged).
  • The Windows Application SDK currently does not provide methods for attaching UI framework content to a AppWindow; you are limited to using the HWND interoperability access methods.
  • Window APIs will not currently work on Windows version 1809 and 1903 for AMD64.

Deployment for unpackaged applications (experimental feature)

This version introduces updates to the dynamic dependencies characteristic, including Bootstrap API.

Important limitations:

  • The dynamic dependencies feature is only supported for unpackaged applications (that is, applications that do not use MSIX for their deployment technology).
  • High callers are not supported.

Other limitations and known issues

  • No support for any processor build configuration: The Windows application SDK is written in native code and therefore does not support Any processor build configurations. WinUI project templates only allow architecture specific builds. When adding the Windows Application SDK to an existing .NET application or component that supports Any processor, you must specify the desired architecture: x86, x64 Where arm64.
  • .NET applications must target build 18362 or higher: Your TFM must be set to net5.0-windows10.0.18362 or higher, and your packaging project must be set to 18362 or higher. For more information, see the known issue on GitHub.

Learn more and find download links from Microsoft here.

Previous FUTEX2 patches sent in a simpler form to help Windows games on Linux
Next Windows 11 Beta: Microsoft is rolling out updates for Windows apps - What apps are included?

No Comment

Leave a reply

Your email address will not be published.