Preview channel release notes for the Windows App SDK 1.5
Article
Important
The preview channel is not supported for use in production environments, and apps that use the preview releases cannot be published to the Microsoft Store.
The preview channel includes releases of the Windows App SDK with preview channel features in late stages of development. Preview releases do not include experimental features and APIs but may still be subject to breaking changes before the next stable release.
There is a behavioral difference between WinAppSDK 1.4 and WinAppSDK 1.5 for Xaml Islands-based apps when the last Xaml Window on any thread is closed.
In WinAppSDK 1.4, the Xaml runtime always exits the thread's event loop when the last Xaml window on a thread is closed.
In WinAppSDK 1.5:
If your app is a WinUI Desktop app, the default behavior is still the same as in WinAppSDK 1.4.
If you're using Xaml for the DesktopWindowXamlSource ("Xaml Islands") API, the default behavior is now that Xaml does not automatically exit the thread's event loop.
In both modes, you can change this behavior by setting the Application.DispatcherShutdownMode property.
For more information, see the documentation for the Application.DispatcherShutdownMode property when available.
There is a behavioral difference between WinAppSDK 1.4 and WinAppSDK 1.5 for Xaml Islands-based apps in the lifetime of the Xaml runtime:
In WinAppSDK 1.4, the Xaml runtime shuts down on a thread if either all WindowsXamlManager and DesktopWindowXamlSource objects on a given thread are closed or shut down, or the DispatcherQueue running on that thread is shut down (the Xaml runtime shuts down during the DispatcherQueue.FrameworkShutdownStarting stage).
In WinAppSDK 1.5, the Xaml runtime shuts down on a thread only when the DispatcherQueue running on that thread is shut down (the Xaml runtime shuts down during the DispatcherQueue.FrameworkShutdownStarting stage).
For more information, see the documentation for the WindowsXamlManager class when available.
WinUI Maps control
The initial release of the WinUI Maps control is now available! This control is powered by WebView2 and Azure Maps, providing the following features:
Panning and zooming with either the map buttons or touch.
Changing the style of the map to satellite, terrain, or street view.
Programmatically adding interactable pins with developer-customizable icons to the map.
Developer customization for where the map is centered on initial load.
Control for developers over hiding or showing the buttons for panning, zooming, and map styles.
Fixed an issue from the 1.5-experimental2 release where the projection DLL was not generated. For more info, see GitHub issue #4152.
Fixed an issue where the ellipsis button on the text formatting popup of the RichEditBox was not displaying the list of actions properly. For more info, see GitHub issue #9140.
Fixed an issue where ListView didn't handle keyboard accelerators properly. For more info, see GitHub issue #8063.
Fixed an access violation issue with using AccessKey to close a window. For more info, see GitHub issue #8648.
Fixed an issue affecting text alignment in a MenuFlyoutItem within a MenuBar. For more info, see GitHub issue #8755.
Fixed an issue where highlighted text would not remain highlighted upon right-click. For more info, see GitHub issue #1801.
Fixed an issue causing inactive windows to crash the app when closed. For more info, see GitHub issue #8913.
Fixed an issue that could hang applications when scrolling with the middle mouse button and left-clicking immediately afterwards. For more info, see GitHub issue #9233.
New APIs in 1.5.0-preview1
Version 1.5-preview1 includes the following new APIs compared to the stable 1.4 release:
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
Windows developer feedback
Windows developer is an open source project. Select a link to provide feedback: