We reported a month ago that Microsoft had just released Windows App SDK 1.0.0-experimental, a toolkit that allows desktop app developers to build apps with a Windows user interface, APIs, and features. modern platforms.
Now Windows App SDK 1.0.0-Preview1 is available for download through Nuget.
SDK version 1.0.0 brings the following features and improvements:
This version of WinUI 3 focuses on building towards 1.0 Stable with bug fixes.
- New features: No new functionality in Preview 1.
- Resolved issues: For the full list of issues fixed in this release, check out our GitHub repository.
For more information or to start developing with WinUI, see:
This release brings the windowing API that we introduced in Experimental 1 to a Preview state. There are no major new features in this release as it focuses on bug fixes, stability, and API signature tweaks. Notable changes and additions are described below.
- DisplayAreaWatcher has been added to the Windowing APIs. This allows a developer to observe changes in the display topology and enumerate the DisplayAreas currently defined in the system.
- AppWindow now supports setting the window icon via the SetIcon method, and AppWindowTitleBar now supports selecting show / hide window icon with the system menu via the IconShowOptions property.
- This version of AppWindow is currently only available for Win32 apps (both packaged and unpackaged).
- The Windows Application SDK currently does not provide methods for attaching UI framework content to an AppWindow; you are limited to using the HWND interoperability access methods.
- Customization of the window title bar works only on Windows 11. Use the IsCustomizationSupported method to verify support for the customization of the title bar feature. We intend to lower this functionality.
For more information, see Manage application windows.
This release brings new functionality to the input API. Notable changes and additions are described below.
New features and updates:
- PointerPredictor gives input latency sensitive applications, such as inking applications, the ability to predict entry point locations up to 15ms into the future to achieve better latency and smooth animation.
- PenDeviceInterop allows you to acquire a reference to Windows.Devices.Input.PenDevice using the FromPointerPoint method.
- InputCursor provides an explicit distinction between predefined system cursor types and custom cursor types by removing the “Custom” type present in
CoreCursor, and divide the
CoreCursorobject into separate objects.
- Updates to the InputCursor APIs.
- This version of the input API has known issues with Windows version 1809.
- MRT Core is not yet supported by any subtype of InputCursor.
Starting with version 1.0 Preview 1, the MRT Core APIs have been moved from the Microsoft.ApplicationModel.Resources namespace to the Microsoft.Windows.ApplicationModel.Resources namespace.
Other limitations and known issues
Learn more and find download links from Microsoft here.