Windows App SDK 2.6.4

[agniuks]

Windows App SDK 2.6.4 removes the Limited Access Feature requirement for the Language Model APIs, updates ONNX Runtime to 1.27.1, and includes reliability fixes across WinUI 3, app lifecycle, notifications, DispatcherQueue, Content, composition, and Windows AI.

What's new in WinAppSDK 2.6.4:

• Language Model APIs no longer require a Limited Access Feature unlock. Apps can call the Language Model APIs without first unlocking the Language Model Limited Access Feature. Apps using earlier Windows App SDK versions must continue to follow the LAF requirements for their target Windows versions.
• Updated ONNX Runtime. The version of ONNX Runtime has been updated to 1.27.1. See ONNX Runtime versions for more info.

Bug fixes:

Bug Fix	Runtime Compatibility Change
Fixed an access violation crash that could occur during app shutdown when a text control, such as a TextBox or RichEditBox, was still alive while the XAML core was being torn down.	CCoreServices_InputServicesTeardownOrder
Fixed an issue where AppInstance.GetInstances could fail with E_INVALIDARG while enumerating application instances.	AppLifecycle_GetInstancesProcessHandleFix
Fixed a crash when calling some AppNotificationManager and AppInstance APIs.	AppNotification_AppInstance_FixStackOverflowCrash
Fixed an issue where self-contained apps could fail to load Microsoft.WindowsAppRuntime.Insights.Resource.dll when using the VersionInfo APIs or registering an AppNotification callback (microsoft/WindowsAppSDK#6071, microsoft/WindowsAppSDK#6387).	VersionInfo_MissingInsightsResourceDll
Fixed an issue where an unhandled exception in a DispatcherQueue callback could produce a crash dump with only the HRESULT, omitting the app's original exception type, message, and stack trace.	DispatcherQueue_CaptureCallbackErrorContext
Fixed the same crash dump issue for unhandled exceptions in DispatcherQueueTimer.Tick event handlers.	DispatcherQueueTimer_CaptureTickErrorContext
Fixed an issue where a failure while creating a ContentIsland or other Content object immediately terminated the app. The original error is now returned to the calling code instead.	ContentIsland_InitializationFailureCleanup
Fixed system backdrop support for lifted content islands and XAML windows when using the System Composition Engine.	SwitcherSystemBackdropBrushSupport
Fixed projection of compatible Windows.UI.Composition objects into Microsoft.UI.Composition, preserving object identity, when using the System Composition Engine.	SwitcherColdWrappingWUCToMUC
Fixed a crash in ItemsView when the target of StartBringItemIntoView was collapsed or recycled before the scroll completed (microsoft/microsoft-ui-xaml#11865).	ItemsView_InvalidBringIntoViewAnchor
Fixed a crash that could occur when a WebView2 control received focus while still initializing and its parent window was temporarily disabled when initialization finished.	WebView2_HandleMoveFocusInvalidArgument
Improved diagnosability for Windows AI model initialization APIs.	AIFabric_Tip_APIClassName_ReasonName
Fixed false IntelliSense errors on XAML-generated members, such as InitializeComponent and x:Name fields, in WinUI 3 C# projects edited in VS Code with C# Dev Kit. To opt out, set the EnableWinUIDesignTimeGeneratedXamlCompileItems property to false.	N/A, build .targets change

To see everything that's new and changed, see the full Windows App SDK 2.6.4 release notes.

Try it out

• Download the 2.6.4 NuGet package to use WinAppSDK 2.6 in your app.
• Download and update the WinUI Gallery to see the WinUI 3 updates firsthand.

Getting started

To get started using Windows App SDK to develop Windows apps, check out the following documentation:

• Install developer tools.
• Create a WinUI 3 app.
• Continue your development journey.

---

This discussion was created from the release Windows App SDK 2.6.4.

[Bogdan Pătrăucean (bogdan-patraucean)]

agniuks no WinUI 3 release?