diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-0.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-0.md index c20817e4b3..28bdf79c04 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-0.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-0.md @@ -35,7 +35,7 @@ zone_pivot_groups: wasdk-release-channels > - Fixed issue causing C# apps with WebView2 to crash on launch when the C/C++ Runtime (CRT) isn't installed. > - Fixed touch input issues causing problems with keyboard shortcuts and other scenarios. For more information, see [issue 6291](https://github.com/microsoft/microsoft-ui-xaml/issues/6291) on GitHub. > -> **Note**: We don't usually add functionality in a servicing release, but this release's WebView2 fix required us to update to the latest version of the WebView2 SDK (1020.46 to 1185.39). See [Release Notes for the WebView2 SDK](/microsoft-edge/webview2/release-notes#10118539) for additional information on WebView2 1.0.1185.39 and [Distribute your app and the WebView2 Runtime](/microsoft-edge/webview2/concepts/distribution) for additional information on the WebView2 Runtime. +> **Note**: We don't usually add functionality in a servicing release, but this release's WebView2 fix required us to update to the latest version of the WebView2 SDK (1020.46 to 1185.39). See [Release Notes for the WebView2 SDK](/microsoft-edge/webview2/release-notes) for additional information on WebView2 1.0.1185.39 and [Distribute your app and the WebView2 Runtime](/microsoft-edge/webview2/concepts/distribution) for additional information on the WebView2 Runtime. @@ -739,7 +739,7 @@ Starting in version 1.0 Preview 1, MRT Core APIs have moved from the [Microsoft. Push notifications (experimental feature) > -> This release introduces a push notifications API that can be used by packaged desktop apps with Azure app registration-based identities. To use this feature, you must [sign up for our private preview](https://aka.ms/windowsappsdk/push-private-preview). +> This release introduces a push notifications API that can be used by packaged desktop apps with Azure app registration-based identities. > > Important limitations: > diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-1.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-1.md index 50081a38a3..0b41811018 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-1.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-1.md @@ -105,7 +105,7 @@ zone_pivot_groups: wasdk-release-channels > **New features:** > > - Mica and Background Acrylic are now available for WinUI applications. -> - For more information about these materials, check out [Materials in Windows 11](../../design/signature-experiences/materials.md). Check out our sample code for applying Mica in C++ applications at [Apply Mica or Acrylic materials in desktop apps for Windows 11](../../windows-app-sdk/system-backdrop-controller.md) and in C# applications [on GitHub](https://github.com/microsoft/WinUI-Gallery/tree/main/WinUIGallery/ControlPagesSampleCode/SystemBackdrops) as part of the [WinUI 3 Gallery](https://apps.microsoft.com/detail/9P3JFPWWDZRC). +> - For more information about these materials, check out [Materials in Windows 11](../../design/signature-experiences/materials.md). Check out our sample code for applying Mica in C++ applications at [Apply Mica or Acrylic materials in desktop apps for Windows 11](../../windows-app-sdk/system-backdrop-controller.md) and in C# applications [on GitHub](https://github.com/microsoft/WinUI-Gallery/tree/winappsdk/1.1/WinUIGallery/ControlPagesSampleCode/SystemBackdrops) as part of the [WinUI 3 Gallery](https://apps.microsoft.com/detail/9P3JFPWWDZRC). > - First introduced in 1.0.1, we have stabilized and enabled the creation of **multiple windows on the same thread** in WinUI applications. See [issue 5918](https://github.com/microsoft/microsoft-ui-xaml/issues/5918) for more information. > > **Fixed bugs:** @@ -288,7 +288,7 @@ zone_pivot_groups: wasdk-release-channels > > Mica and Background Acrylic are now available for WinUI applications. > -> For more information about these materials, check out [Materials in Windows 11](../../design/signature-experiences/materials.md). Check out our sample code for applying Mica in C++ applications at [Apply Mica or Acrylic materials in desktop apps for Windows 11](../../windows-app-sdk/system-backdrop-controller.md) and in C# applications [on GitHub](https://github.com/microsoft/WinUI-Gallery/tree/main/WinUIGallery/ControlPagesSampleCode/SystemBackdrops) as part of the WinUI Controls Gallery. +> For more information about these materials, check out [Materials in Windows 11](../../design/signature-experiences/materials.md). Check out our sample code for applying Mica in C++ applications at [Apply Mica or Acrylic materials in desktop apps for Windows 11](../../windows-app-sdk/system-backdrop-controller.md) and in C# applications [on GitHub](https://github.com/microsoft/WinUI-Gallery/tree/winappsdk/1.1/WinUIGallery/ControlPagesSampleCode/SystemBackdrops) as part of the WinUI Controls Gallery. > diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-2.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-2.md index eda254498a..152fe5c4a8 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-2.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-2.md @@ -31,9 +31,9 @@ zone_pivot_groups: wasdk-release-channels
Bug fixes > - Fixed issue causing self-contained apps to not be able to set UAC Settings. For more information, see GitHub issue [#3376](https://github.com/microsoft/WindowsAppSDK/issues/3376). -> - Fixed issue causing push notifications to return an inaccurate Expiration time with `PushNotificationChannel::ExpirationTime`. For more information, see GitHub issue [#3300](https://github.com/microsoft/WindowsAppSDK/issues/3330). +> - Fixed issue causing push notifications to return an inaccurate Expiration time with `PushNotificationChannel::ExpirationTime`. For more information, see GitHub issue [#3330](https://github.com/microsoft/WindowsAppSDK/issues/3330). > - Fixed issue causing negative numbers to be considered "invalid" when passing a double as a parameter into an x:Bind function. -> - Several fixes to update the WinUI VSIX. These updates included simplifying the project template dipAwareness in app.manifest, removing the UWP templates, updating localized resource files, adding the phone id to unblock store submission, and removing the copyright notice and license. For more info see GitHub issues [#5659](https://github.com/microsoft/microsoft-ui-xaml/issues/5659), [#3205](https://github.com/microsoft/WindowsAppSDK/issues/3205), [#3323](https://github.com/microsoft/WindowsAppSDK/issues/3323), [#3322](https://github.com/microsoft/WindowsAppSDK/issues/3322), [#3143](https://github.com/microsoft/WindowsAppSDK/issues/3143). +> - Several fixes to update the WinUI VSIX. These updates included simplifying the project template dpiAwareness in app.manifest, removing the UWP templates, updating localized resource files, adding the phone id to unblock store submission, and removing the copyright notice and license. For more info see GitHub issues [#5659](https://github.com/microsoft/microsoft-ui-xaml/issues/5659), [#3205](https://github.com/microsoft/WindowsAppSDK/issues/3205), [#3323](https://github.com/microsoft/WindowsAppSDK/issues/3323), [#3322](https://github.com/microsoft/WindowsAppSDK/issues/3322), [#3143](https://github.com/microsoft/WindowsAppSDK/issues/3143).
@@ -137,7 +137,7 @@ zone_pivot_groups: wasdk-release-channels
Support for Visual Studio Arm64 -> As early as Project Reunion (now Windows App SDK) 0.5, apps developed with Windows App SDK were able to run on Arm64. Starting with Visual Studio 17.3 Preview 2, you can develop native applications with Windows App SDKpp SDK on Arm64 devices. +> As early as Project Reunion (now Windows App SDK) 0.5, apps developed with Windows App SDK were able to run on Arm64. Starting with Visual Studio 17.3 Preview 2, you can develop native applications with Windows App SDK on Arm64 devices. > > To get started developing on an Arm64 device, see [Windows on Arm](/windows/arm/overview) and [Arm64 Visual Studio](https://devblogs.microsoft.com/visualstudio/arm64-visual-studio/). @@ -170,7 +170,7 @@ zone_pivot_groups: wasdk-release-channels
Windowing -> Full title bar customization is now available on Windows 10, version 1809 and later through the [**AppWindowTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar) class. You can set [**AppWindowTitleBar.ExtendsContentIntoTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.extendscontentintotitlebar) to `true` to extend content into the title bar area, and [**SetDragRectangles**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.setdragrectangles#microsoft-ui-windowing-appwindowtitlebar-setdragrectangles(windows-graphics-rectint32())) to define drag regions (in addition to other customization options). +> Full title bar customization is now available on Windows 10, version 1809 and later through the [**AppWindowTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar) class. You can set [**AppWindowTitleBar.ExtendsContentIntoTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.extendscontentintotitlebar) to `true` to extend content into the title bar area, and [**SetDragRectangles**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.setdragrectangles) to define drag regions (in addition to other customization options). > > If you've been using the [**AppWindowTitleBar.IsCustomizationSupported**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.iscustomizationsupported) property to check whether you can call the [**AppWindowTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar) APIs, it now returns `true` on supported Windows App SDK Windows 10 versions (1809 and later). > @@ -317,7 +317,7 @@ zone_pivot_groups: wasdk-release-channels
Windowing > -> Full title bar customization is now available on Windows 10, version 1809 and later through the [**AppWindowTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar) class. You can set [**AppWindowTitleBar.ExtendsContentIntoTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.extendscontentintotitlebar) to `true` to extend content into the title bar area, and [**SetDragRectangles**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.setdragrectangles#microsoft-ui-windowing-appwindowtitlebar-setdragrectangles(windows-graphics-rectint32())) to define drag regions (in addition to other customization options). +> Full title bar customization is now available on Windows 10, version 1809 and later through the [**AppWindowTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar) class. You can set [**AppWindowTitleBar.ExtendsContentIntoTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.extendscontentintotitlebar) to `true` to extend content into the title bar area, and [**SetDragRectangles**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.setdragrectangles) to define drag regions (in addition to other customization options). > > If you've been using the [**AppWindowTitleBar.IsCustomizationSupported**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar.iscustomizationsupported) property to check whether you can call the [**AppWindowTitleBar**](/windows/windows-app-sdk/api/winrt/microsoft.ui.windowing.appwindowtitlebar) APIs, it now returns `true` on supported Windows App SDK Windows 10 versions (1809 and later). > diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-4.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-4.md index 5b3e3b1993..f49f378a97 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-4.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-4.md @@ -180,7 +180,7 @@ zone_pivot_groups: wasdk-release-channels > - A new `ThemeSettings` class that allows Win32 WinRT apps to detect when the system's High Contrast setting has changed, similar to UWP's [AccessibilitySettings](/uwp/api/windows.ui.viewmanagement.accessibilitysettings) class. See the [ThemeSettings API spec](https://github.com/microsoft/WindowsAppSDK/blob/main/specs/themes/ThemeSettings.md) on GitHub for more information. > - `AccessKeyManager.EnterDisplayMode` is a new method to display access keys for the current focused element of a provided root. Access keys are in "display mode" when showing a key tip to invoke a command, such as pressing the Alt key in Paint to show what keys correspond to what controls. This method allows for programmatically entering display mode. > - `Application.ResourceManagerRequested` provides a mechanism to provide a different `IResourceManager` to resolve resource URIs for scenarios when the default `ResourceManager` won't work. For more information, see the [Application.ResourceManagerRequested API spec](https://github.com/microsoft/microsoft-ui-xaml/blob/main/specs/custom-iresourcemanager-spec.md) on GitHub. -> - The version of the WebView2 SDK was updated from 1661.34 to [1823.32](/microsoft-edge/webview2/release-notes?tabs=winrtcsharp#10182332). +> - The version of the WebView2 SDK was updated from 1661.34 to [1823.32](/microsoft-edge/webview2/release-notes?tabs=winrtcsharp). > - `Popup/FlyoutBase.IsConstrainedToRootBounds = false` is now supported, allowing a popup/flyout to extend outside the bounds of the parent window. A `SystemBackdrop` property has been added to these types to support having acrylic in these unconstrained popups. Menus by default use this to have acrylic. > - `Closed`, `FrameworkClosed`, and `IsClosed` have been added to `DesktopAcrylicController` and `MicaController` to improve handling during object/thread shutdown. > - `DesktopAcrylicController.Kind` can now be set to choose between some standard acrylic appearances. @@ -201,7 +201,7 @@ zone_pivot_groups: wasdk-release-channels > - There are some new continuable exceptions when hiding `ShouldConstrainToRootBounds="False"` popups/flyouts. That includes hiding tooltips, as reported here: [Dismissing a tooltip throws 4 native exceptions · Issue #8699 · microsoft/microsoft-ui-xaml (github.com)](https://github.com/microsoft/microsoft-ui-xaml/issues/8699) > - In 1.4, the min/max/close caption buttons for `ExtendsContentIntoTitleBar = true` are now drawn by AppWindow rather than XAML. This is by design, but it can impact apps that were overriding XAML's internal styles to hide or do extra customization of these buttons, such as in this report: [Cannot hide caption button on titlebar · Issue #8705 · microsoft/microsoft-ui-xaml (github.com)](https://github.com/microsoft/microsoft-ui-xaml/issues/8705) > - There was a breaking change in .NET 8 to how it handles the runtime identifier graph: [[Breaking change]: Projects targeting .NET 8 and higher will by default use a smaller, portable RID graph. · Issue #36527 · dotnet/docs (github.com)](https://github.com/dotnet/docs/issues/36527). Because of this issue and because .NET 8 has not officially released yet, the Windows App SDK 1.4 does not officially support .NET 8. However, if you would still like to target the pre-release version of .NET 8 with this version of the App SDK, we recommend the following steps: -> - [Setting UseRidGraph to true](/dotnet/core/compatibility/deployment/8.0/rid-asset-list#recommended-action) is recommended. You'll also need to update the `` property in the `.csproj` file to `win-x86;win-x64;win-arm64`, as well as update each `Propeties\*pubxml` file to switch from `win10` to `win` in the `` property (for example, `win-x86`). +> - [Setting UseRidGraph to true](/dotnet/core/compatibility/deployment/8.0/rid-asset-list#recommended-action) is recommended. You'll also need to update the `` property in the `.csproj` file to `win-x86;win-x64;win-arm64`, as well as update each `Properties\*pubxml` file to switch from `win10` to `win` in the `` property (for example, `win-x86`). > - With Windows App SDK 1.4, the target `GenerateDeploymentManagerCS` in `Microsoft.WindowsAppSDK.DeploymentManager.CS.targets` was renamed to `GenerateBootstrapCS`. > - `MenuFlyout` background doesn't use the application's requested theme: > - [MenuFlyoutItem text doesn't sync with system theme. · Issue #8678 · microsoft/microsoft-ui-xaml (github.com)](https://github.com/microsoft/microsoft-ui-xaml/issues/8678) @@ -544,7 +544,7 @@ zone_pivot_groups: wasdk-release-channels > - `AccessKeyManager.EnterDisplayMode` is a new method to display access keys for the current focused element of a provided root. Access keys are in "display mode" when showing a key tip to invoke a command, such as pressing the Alt key in Paint to show what keys correspond to what controls. This method allows for programmatically entering display mode. > - `Application.ResourceManagerRequested` provides a mechanism to provide a different `IResourceManager` to resolve resource URIs for scenarios when the default `ResourceManager` won't work. For more information, see the [Application.ResourceManagerRequested API spec](https://github.com/microsoft/microsoft-ui-xaml/blob/main/specs/custom-iresourcemanager-spec.md) on GitHub. > - We're introducing a new list control called the `ItemsView` and a corresponding concrete `ItemContainer` class. `ItemContainer` is a lightweight container with built-in selection states and visuals, which can easily wrap desired content and be used with `ItemsView` for a collection control scenario. `ItemsView` is still marked experimental in Preview 1 but will be included in the next 1.4 release. -> - The version of the WebView2 SDK was updated from 1661.34 to [1823.32](/microsoft-edge/webview2/release-notes?tabs=winrtcsharp#10182332). +> - The version of the WebView2 SDK was updated from 1661.34 to [1823.32](/microsoft-edge/webview2/release-notes?tabs=winrtcsharp). >
diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-5.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-5.md index a5f6531131..7c6712c9dd 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-5.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-5.md @@ -356,7 +356,7 @@ zone_pivot_groups: wasdk-release-channels > > - Fixed an issue where `StackPanel` applied spacing to collapsed items. For more info, see GitHub issue [#916](https://github.com/microsoft/microsoft-ui-xaml/issues/916). -> - Fixed problems with scrolling controls no longer working after closing another app window. Fore more info, see GitHub issues [#9292](https://github.com/microsoft/microsoft-ui-xaml/issues/9292) and [#9355](https://github.com/microsoft/microsoft-ui-xaml/issues/9355). +> - Fixed problems with scrolling controls no longer working after closing another app window. For more info, see GitHub issues [#9292](https://github.com/microsoft/microsoft-ui-xaml/issues/9292) and [#9355](https://github.com/microsoft/microsoft-ui-xaml/issues/9355). > - Fixed a crash when setting `DebugSettings.EnableFrameRateCounter` to *true* before the first frame rendered. For more info, see GitHub issue [#2835](https://github.com/microsoft/microsoft-ui-xaml/issues/2835). > - Fixed a potential compile error for C++ where some headers did not include necessary dependencies. Note that the change of `#include` order might impact some apps, such as possibly causing a compile error for `IInspectable` if the app is using a version of C++/WinRT older than 2023. For more info, see GitHub issue [#9014](https://github.com/microsoft/microsoft-ui-xaml/issues/9014). > - Fixed an issue where `ElementName` bindings didn't work inside the `ItemsRepeater` `DataTemplate`. For more info, see GitHub issue [#560](https://github.com/microsoft/microsoft-ui-xaml/issues/560). @@ -641,7 +641,7 @@ zone_pivot_groups: wasdk-release-channels New APIs for 1.5-experimental2 > -> 1.5-experimental2 includes the following new APIs. These APIs are not experimental, but are not yet included in a stable release version of the Windows App SDKpp SDK. +> 1.5-experimental2 includes the following new APIs. These APIs are not experimental, but are not yet included in a stable release version of the Windows App SDK. > > ```C# > Microsoft.Graphics.DirectX diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-6.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-6.md index 8408d876dd..a0460e7fb8 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-6.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-6.md @@ -36,7 +36,7 @@ zone_pivot_groups: wasdk-release-channels
Bug Fixes -> - Fixed PackageDeploymentManager telemetry to properly capture when completion status. For more info, see GitHub issue [#5297](https://github.com/microsoft/WindowsAppSDK/pull/5297). +> - Fixed PackageDeploymentManager telemetry to properly capture completion status. For more info, see GitHub PR [#5297](https://github.com/microsoft/WindowsAppSDK/pull/5297). > - Fixed a crash when using pen input on an x86 app. > - Fixed a potential crash if the window is already destroyed when WinUI is attempting to initialize for scrolling. > - Fixed the WINDOWSAPPSDK_RELEASE_PATCH define and Microsoft::WindowsAppSDK::Release::Patch values in WindowsAppSDK-VersionInfo.h to not always be 0. The define is now the yymmdd date of the build, and the Patch value is the mmdd date. This change provides better runtime information on the version being used without changing any variable sizes or the version scheme. @@ -50,7 +50,7 @@ zone_pivot_groups: wasdk-release-channels
Bug Fixes -- Improved the telemetry for failure scenarios in `WindowsAppRuntimeInstall-.exe`. For more info, see GitHub issue [#5291](https://github.com/microsoft/WindowsAppSDK/pull/5291). +- Improved the telemetry for failure scenarios in `WindowsAppRuntimeInstall-.exe`. For more info, see GitHub PR [#5291](https://github.com/microsoft/WindowsAppSDK/pull/5291). - Fixed an issue where pointer input would stop working when using arrow keys at the same time. For more info, see GitHub issue [#10126](https://github.com/microsoft/microsoft-ui-xaml/issues/10126). - Fixed an issue where apps in remote desktop stop responding to pointer input. For more info, see GitHub issue [#10009](https://github.com/microsoft/microsoft-ui-xaml/issues/10009). (This is the same fix as the pointer input plus arrow keys fix, due to remote desktop automatically sending some key input during the switch away and back.) - Fixed a potential crash trying to restore focus if a window activation event is delivered for a window which is closing. @@ -59,7 +59,7 @@ zone_pivot_groups: wasdk-release-channels - Fixed a potential crash if `ProgressBar::SetProgressBarIndicatorWidth` is called on a ProgressBar which is not in the tree. - Fixed a potential crash caused by `CPopup::EnsureBridgeClosed` sometimes triggering reentrancy. - Fixed a potential crash when closing a popup due to `CUIElement::FlushPendingKeepVisibleOperations` using a null children collection. -- Fixed `PackageDeploymentManager.EnsurePackage*Ready` to ensure version supersedence. For more info, see GitHub issue [#5225](https://github.com/microsoft/WindowsAppSDK/pull/5225). +- Fixed `PackageDeploymentManager.EnsurePackage*Ready` to ensure version supersedence. For more info, see GitHub PR [#5225](https://github.com/microsoft/WindowsAppSDK/pull/5225).
@@ -106,7 +106,7 @@ Microsoft.Windows.Widgets.Providers
Bug Fixes - Fixed an issue with text selection highlighting in a multi-line TextBox. For more info, see GitHub issue [#9965](https://github.com/microsoft/microsoft-ui-xaml/issues/9965). - Fixed an issue where the DDLM package would sometimes not install, preventing launch of unpackaged apps. For more info, see GitHub issue [#3855](https://github.com/microsoft/WindowsAppSDK/issues/3855). -- Fixed a potential crash in Detours in some scenarios. For more info, see GitHub issue [#4937](https://github.com/microsoft/WindowsAppSDK/pull/4937). +- Fixed a potential crash in Detours in some scenarios. For more info, see GitHub PR [#4937](https://github.com/microsoft/WindowsAppSDK/pull/4937). - Fixed another potential issue where a menu off a CommandBar may incorrectly open up instead of down when the CommandBar is at the bottom of the window. - Fixed a potential crash when running on older graphics hardware. - Fixed a potential crash in pointer event handling when closing a window. @@ -261,7 +261,7 @@ Microsoft.Windows.Widgets.Providers > > ``` > -> For complete root descriptor XML expression syntax, see [Root Descriptors](/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-8-0#root-descriptors). +> For complete root descriptor XML expression syntax, see [Root Descriptors](/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-8-0). > > [!NOTE] > Dependency packages that have not yet adopted AOT support may exhibit runtime issues. @@ -299,7 +299,7 @@ Microsoft.Windows.Widgets.Providers > > - Added a new `ColorHelper.ToDisplayName()` API, filling that gap from UWP. -> - Added a new `Microsoft.Windows.Globalization.ApplicationLanguages` class, which notably includes a new `PrimaryLanguageOverride` feature. For more info, see GitHub issue [#4523](https://github.com/microsoft/WindowsAppSDK/pull/4523). +> - Added a new `Microsoft.Windows.Globalization.ApplicationLanguages` class, which notably includes a new `PrimaryLanguageOverride` feature. For more info, see GitHub PR [#4523](https://github.com/microsoft/WindowsAppSDK/pull/4523). > - Unsealed `ItemsWrapGrid`. This should be a backward-compatible change. > - `PipsPager` supports a new mode where it can wrap between the first and last items. > @@ -378,7 +378,7 @@ Microsoft.Windows.Widgets.Providers > - Fixed an issue where SVG files defining a negative viewbox no longer rendered. For more info, see GitHub issue [#9415](https://github.com/microsoft/microsoft-ui-xaml/issues/9415). > - Fixed an issue where changing `ItemsView.Layout` orientation caused an item to be removed. For more info, see GitHub issue [#9422](https://github.com/microsoft/microsoft-ui-xaml/issues/9422). > - Fixed an issue where scrolling a `ScrollView` generated a lot of debug output. For more info, see GitHub issue [#9434](https://github.com/microsoft/microsoft-ui-xaml/issues/9434). -> - Fixed an issue where `MapContorl.InteractiveControlsVisible` did not work properly. For more info, see GitHub issue [#9486](https://github.com/microsoft/microsoft-ui-xaml/issues/9486). +> - Fixed an issue where `MapControl.InteractiveControlsVisible` did not work properly. For more info, see GitHub issue [#9486](https://github.com/microsoft/microsoft-ui-xaml/issues/9486). > - Fixed an issue where `MapControl.MapElementClick` event didn't properly fire. For more info, see GitHub issue [#9487](https://github.com/microsoft/microsoft-ui-xaml/issues/9487). > - Fixed an issue where x:Bind didn't check for null before using a weak reference, which could result in a crash. For more info, see GitHub issue [#9551](https://github.com/microsoft/microsoft-ui-xaml/issues/9551). > - Fixed an issue where changing the `TeachingTip.Target` property didn't correctly update its position. For more info, see GitHub issue [#9553](https://github.com/microsoft/microsoft-ui-xaml/issues/9553). @@ -585,7 +585,7 @@ For the updated runtime and MSIX, see [Downloads for the Windows App SDK](../../ Native AOT support > -> The .NET `PublishAot` project property is now supported for native Ahead-Of-Time compilation. For details on Native AOT, see [Native AOT Deployment](/dotnet/core/deploying/native-aot/). Because AOT builds on Trimming support, much of the Trimming-related guidance previously described in the 1.6-experimental1 release applies as well. See [Native AOT support](/windows/apps/windows-app-sdk/experimental-channel#native-aot-support) for more info. +> The .NET `PublishAot` project property is now supported for native Ahead-Of-Time compilation. For details on Native AOT, see [Native AOT Deployment](/dotnet/core/deploying/native-aot/). Because AOT builds on Trimming support, much of the Trimming-related guidance previously described in the 1.6-experimental1 release applies as well. See [Native AOT support](/windows/apps/windows-app-sdk/experimental-channel) for more info. > > As noted above, C# projects should have a package reference to [Microsoft.Windows.CsWinRT](https://www.nuget.org/packages/Microsoft.Windows.CsWinRT) 2.1.1 (or later).This version includes an AOT-safe `ICustomPropertyProvider` implementation. Types used with this support should be marked with the `WinRT.GeneratedBindableCustomProperty` attribute along with being made `partial`. > @@ -624,9 +624,9 @@ For the updated runtime and MSIX, see [Downloads for the Windows App SDK](../../ > > - We added a new `ColorHelper.ToDisplayName()` API, filling that gap from UWP. -> - Added a new `Microsoft.Windows.Globalization.ApplicationLanguages` class, which notably includes a new `PrimaryLanguageOverride` feature. For more info, see GitHub issue [#4523](https://github.com/microsoft/WindowsAppSDK/pull/4523). +> - Added a new `Microsoft.Windows.Globalization.ApplicationLanguages` class, which notably includes a new `PrimaryLanguageOverride` feature. For more info, see GitHub PR [#4523](https://github.com/microsoft/WindowsAppSDK/pull/4523). > - Unsealed `ItemsWrapGrid`. This should be a backward-compatible change. -> - `PipsPager` supports a new mode where it can wrap between the first and list items. +> - `PipsPager` supports a new mode where it can wrap between the first and last items. > - `RatingControl` is now more customizable, by moving some hard-coded style properties to theme resources. This allows apps to override these values to better customize the appearance of RatingControl. > @@ -688,7 +688,7 @@ For the updated runtime and MSIX, see [Downloads for the Windows App SDK](../../ > - Fixed an issue where SVG files defining a negative viewbox no longer rendered. For more info, see GitHub issue [#9415](https://github.com/microsoft/microsoft-ui-xaml/issues/9415). > - Fixed an issue where changing `ItemsView.Layout` orientation caused an item to be removed. For more info, see GitHub issue [#9422](https://github.com/microsoft/microsoft-ui-xaml/issues/9422). > - Fixed an issue where scrolling a `ScrollView` generated a lot of debug output. For more info, see GitHub issue [#9434](https://github.com/microsoft/microsoft-ui-xaml/issues/9434). -> - Fixed an issue where `MapContorl.InteractiveControlsVisible` did not work properly. For more info, see GitHub issue [#9486](https://github.com/microsoft/microsoft-ui-xaml/issues/9486). +> - Fixed an issue where `MapControl.InteractiveControlsVisible` did not work properly. For more info, see GitHub issue [#9486](https://github.com/microsoft/microsoft-ui-xaml/issues/9486). > - Fixed an issue where `MapControl.MapElementClick` event didn't properly fire. For more info, see GitHub issue [#9487](https://github.com/microsoft/microsoft-ui-xaml/issues/9487). > - Fixed an issue where x:Bind didn't check for null before using a weak reference, which could result in a crash. For more info, see GitHub issue [#9551](https://github.com/microsoft/microsoft-ui-xaml/issues/9551). > - Fixed an issue where changing the `TeachingTip.Target` property didn't correctly update its position. For more info, see GitHub issue [#9553](https://github.com/microsoft/microsoft-ui-xaml/issues/9553). @@ -847,7 +847,7 @@ For the updated runtime and MSIX, see [Downloads for the Windows App SDK](../../ > - Starting with 1.6-experimental2, the latest WinUI 3 source will now publish to the main branch in the microsoft-ui-xaml GitHub repo, which will enable source searching in that repo. > - We added a new `ColorHelper.ToDisplayName()` API, filling that gap from UWP. > - **Known issue:** Some language translations have character encoding issues. This will be fixed in the next 1.6 release. -> - Added a new `Microsoft.Windows.Globalization.ApplicationLanguages` class, which notably includes a new `PrimaryLanguageOverride` feature. For more info, see GitHub issue [#4523](https://github.com/microsoft/WindowsAppSDK/pull/4523). +> - Added a new `Microsoft.Windows.Globalization.ApplicationLanguages` class, which notably includes a new `PrimaryLanguageOverride` feature. For more info, see GitHub PR [#4523](https://github.com/microsoft/WindowsAppSDK/pull/4523). > - New extensions enable Widget Providers to provide Widgets with web content and announcements for Widgets. > @@ -1336,7 +1336,7 @@ To download, retarget your Windows App SDK NuGet version to `1.6.240531000-exper > > ``` > -> For complete root descriptor XML expression syntax, see [Root Descriptors](/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-8-0#root-descriptors). +> For complete root descriptor XML expression syntax, see [Root Descriptors](/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-8-0). > > [!NOTE] > Dependency packages that have not yet adopted AOT support may exhibit runtime issues. @@ -1405,7 +1405,7 @@ To download, retarget your Windows App SDK NuGet version to `1.6.240531000-exper > > - Unsealed `ItemsWrapGrid`. This should be a backward-compatible change. -> - `PipsPager` supports a new mode where it can wrap between the first and list items. +> - `PipsPager` supports a new mode where it can wrap between the first and last items. > - `RatingControl` is now more customizable, by moving some hard-coded style properties to theme resources. This allows apps to override these values to better customize the appearance of RatingControl. > @@ -1571,7 +1571,7 @@ To download, retarget your Windows App SDK NuGet version to `1.6.240531000-exper > - Fixed an issue where SVG files defining a negative viewbox no longer rendered. For more info, see GitHub issue [#9415](https://github.com/microsoft/microsoft-ui-xaml/issues/9415). > - Fixed an issue where changing `ItemsView.Layout` orientation caused an item to be removed. For more info, see GitHub issue [#9422](https://github.com/microsoft/microsoft-ui-xaml/issues/9422). > - Fixed an issue where scrolling a `ScrollView` generated a lot of debug output. For more info, see GitHub issue [#9434](https://github.com/microsoft/microsoft-ui-xaml/issues/9434). -> - Fixed an issue where `MapContorl.InteractiveControlsVisible` does not work properly. For more info, see GitHub issue [#9486](https://github.com/microsoft/microsoft-ui-xaml/issues/9486). +> - Fixed an issue where `MapControl.InteractiveControlsVisible` does not work properly. For more info, see GitHub issue [#9486](https://github.com/microsoft/microsoft-ui-xaml/issues/9486). > - Fixed an issue where `MapControl.MapElementClick` event doesn't properly fire. For more info, see GitHub issue [#9487](https://github.com/microsoft/microsoft-ui-xaml/issues/9487). > - Fixed an issue where x:Bind doesn't check for null before using a weak reference, which can result in a crash. For more info, see GitHub issue [#9551](https://github.com/microsoft/microsoft-ui-xaml/issues/9551). > - Fixed an issue where changing the `TeachingTip.Target` property doesn't correctly update its position. For more info, see GitHub issue [#9553](https://github.com/microsoft/microsoft-ui-xaml/issues/9553). diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-7.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-7.md index 7591dbcd73..6f5ebcef27 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-7.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-7.md @@ -184,24 +184,24 @@ Released: **November 11, 2025**

> ##### Image Description > The Image Description APIs enable the generation of textual descriptions of images. The length and type of these descriptions can be configured to meet accessibility requirements, ranging from short captions to long descriptions. > -> For additional details, see [What can I do with Image Description?](/windows/ai/apis/imaging#what-can-i-do-with-image-description) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref). +> For additional details, see [What can I do with Image Description?](/windows/ai/apis/imaging) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref). > > ##### Text Recognition > -> Text recognition, also known as optical character recognition (OCR), detects and extracts text within images, converting it into machine-readable character streams. These APIs identify characters, words, lines, polygonal text boundaries, and provide confidence levels for each match. Benefiting from NPU-assisted acceleration, the Windows AI AI-assisted APIs perform faster and more accurately than the legacy [Windows.Media.Ocr.OcrEngine](/uwp/api/windows.media.ocr.ocrengine) APIs. +> Text recognition, also known as optical character recognition (OCR), detects and extracts text within images, converting it into machine-readable character streams. These APIs identify characters, words, lines, polygonal text boundaries, and provide confidence levels for each match. Benefiting from NPU-assisted acceleration, the Windows AI-assisted APIs perform faster and more accurately than the legacy [Windows.Media.Ocr.OcrEngine](/uwp/api/windows.media.ocr.ocrengine) APIs. > > For additional details, see [Get Started with Text Recognition (OCR) in the Windows App SDK](/windows/ai/apis/text-recognition) and [API ref for AI-backed Text Recognition (OCR) in the Windows App SDK](/windows/ai/apis/text-recognition-api-ref). > > ##### Image Super Resolution > The 'ImageScaler' APIs can increase the sharpness and clarity of an image and upscale the image by up to 8x its original resolution. > -> For additional details, see [What can I do with Image Super Resolution?](/windows/ai/apis/imaging#what-can-i-do-with-image-super-resolution) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref). +> For additional details, see [What can I do with Image Super Resolution?](/windows/ai/apis/imaging) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref). > > ##### Image Segmentation > > The Image Segmentation APIs allow for the identification of specific objects within an image. By inputting an image and a "hints" object, the model returns a mask of the identified object. > -> For additional details, see [What can I do with Image Segmentation?](/windows/ai/apis/imaging#what-can-i-do-with-image-segmentation) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref). +> For additional details, see [What can I do with Image Segmentation?](/windows/ai/apis/imaging) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref). >
@@ -217,11 +217,11 @@ Released: **November 11, 2025**

Bugfixes > -> - Fixed PackageDeploymentManager telemetry to properly capture completion status. For more info, see GitHub issue [#5296](https://github.com/microsoft/WindowsAppSDK/pull/5296). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A) +> - Fixed PackageDeploymentManager telemetry to properly capture completion status. For more info, see GitHub PR [#5296](https://github.com/microsoft/WindowsAppSDK/pull/5296). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A) > - Fixed a crash when using pen input on an x86 app. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): InputStateManager_PenInputCrashX86) > - Fixed a potential crash if the window is already destroyed when WinUI is attempting to initialize for scrolling. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): ActivateDirectManipulationManager_CheckCanInit) > - Fixed the WINDOWSAPPSDK_RELEASE_PATCH define and Microsoft::WindowsAppSDK::Release::Patch values in WindowsAppSDK-VersionInfo.h to not always be 0. The define is now the yymmdd date of the build, and the Patch value is the mmdd date. This change provides better runtime information on the version being used without changing any variable sizes or the version scheme. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A, header change) -> - Fixed a potential issue in the Bootstrapper if it is used to load a 1.6 or earlier version of Windows App SDK. For more info, see GitHub issue [#5349](https://github.com/microsoft/WindowsAppSDK/pull/5349). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A) +> - Fixed a potential issue in the Bootstrapper if it is used to load a 1.6 or earlier version of Windows App SDK. For more info, see GitHub PR [#5349](https://github.com/microsoft/WindowsAppSDK/pull/5349). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A) > - Fixed an issue where using MSBuild to build a single-project app could incorrectly fail with a build error if it didn't have a correct launchSettings.json. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A, build .targets change) > - Improved the performance of rendering the first frame on application launch. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): DwmCoreI_OptimizeFirstFrameLatency) > @@ -311,7 +311,7 @@ Released: **November 11, 2025**

Bugfixes > -> - Improved the telemetry for failure scenarios in WindowsAppRuntimeInstall-<arch>.exe. For more info, see GitHub issue [#5289](https://github.com/microsoft/WindowsAppSDK/pull/5289). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A, installer change). +> - Improved the telemetry for failure scenarios in WindowsAppRuntimeInstall-<arch>.exe. For more info, see GitHub PR [#5289](https://github.com/microsoft/WindowsAppSDK/pull/5289). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): N/A, installer change). > - Fixed an issue where pointer input would stop working when using arrow keys at the same time. For more info, see GitHub issue [#10126](https://github.com/microsoft/microsoft-ui-xaml/issues/10126). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixStuckPointerInputQueue). > - Fixed an issue where apps in remote desktop stop responding to pointer input. For more info, see GitHub issue [#10009](https://github.com/microsoft/microsoft-ui-xaml/issues/10009). (This is the same fix as the pointer input plus arrow keys fix, due to remote desktop automatically sending some key input during the switch away and back.) ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixStuckPointerInputQueue). > - Fixed a potential crash trying to restore focus if a window activation event is delivered for a window which is closing. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixWindowCloseFocusCrash) @@ -319,7 +319,7 @@ Released: **November 11, 2025**

> - Fixed a potential crash if ProgressBar::SetProgressBarIndicatorWidth is called on a ProgressBar which is not in the tree. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixSetProgressBarIndicatorWidthCrash) > - Fixed a potential crash caused by CPopup::EnsureBridgeClosed sometimes triggering reentrancy. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixPopupClosingReentrancyCrash) > - Fixed a potential crash when closing a popup due to CUIElement::FlushPendingKeepVisibleOperations using a null children collection. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixPopupUnloadingCrash) -> - Fixed PackageDeploymentManager.EnsurePackage\*Ready to ensure version supersedence. For more info, see GitHub issue [#5191](https://github.com/microsoft/WindowsAppSDK/pull/5191). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): EnsurePackageReadyVersionSupercedence) +> - Fixed PackageDeploymentManager.EnsurePackage\*Ready to ensure version supersedence. For more info, see GitHub PR [#5191](https://github.com/microsoft/WindowsAppSDK/pull/5191). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): EnsurePackageReadyVersionSupercedence) > - Fixed a potential crash caused by WebView2::UpdateCoreWebViewVisibility sometimes triggering reentrancy. For more info, see GitHub issue [#10305](https://github.com/microsoft/microsoft-ui-xaml/issues/10305). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixWebViewVisibilityReentrancyCrash) > - Fixed an issue where app UI sometimes permanently freezes and can stop rendering due to the DispatcherQueue getting stuck. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): FixRandomUIFreezeInDispatcher) > @@ -854,7 +854,7 @@ Released: **November 11, 2025**

> > Using the 'ImageScaler' APIs you can increase the sharpness and clarity of an image and upscale the image up to 8x its original resolution. > -> See [What can I do with Image Super Resolution?](/windows/ai/apis/imaging#what-can-i-do-with-image-super-resolution) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref) to get started. +> See [What can I do with Image Super Resolution?](/windows/ai/apis/imaging) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref) to get started. > > #### Image Description > @@ -863,13 +863,13 @@ Released: **November 11, 2025**

> [!NOTE] > When calling ImageDescriptionGenerator.DescribeAsync() in a Debug build, an error may occur that can be mitigated by continuing the build in Visual Studio. > -> See [What can I do with Image Description?](/windows/ai/apis/imaging#what-can-i-do-with-image-description) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref) to learn more. +> See [What can I do with Image Description?](/windows/ai/apis/imaging) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref) to learn more. > > #### Image Segmentation > > Using Image Segmentation APIs you can identify specific objects within an image. The model takes both an image and a "hints" object and returns a mask of the identified object. > -> See [What can I do with Image Segmentation?](/windows/ai/apis/imaging#what-can-i-do-with-image-segmentation) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref) to get started. +> See [What can I do with Image Segmentation?](/windows/ai/apis/imaging) and [API ref for AI imaging features in the Windows App SDK](/windows/ai/apis/imaging-api-ref) to get started. >
diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-8.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-8.md index 213e78c0f1..a7fbc979cf 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-8.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-1-8.md @@ -34,7 +34,7 @@ Released: **February 10, 2026**

> * Fixed an issue where `CompositionIsland.StateChanged` event handlers were not triggered when the user modified the size of a window by dragging it to the top of the screen or using the edges of the screen and the window has a non-default `TitleBar` with an `IconSource` set. Closing #[#10374](https://github.com/microsoft/microsoft-ui-xaml/issues/10374) ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): InputNonClientPointerSource_PropagateWindowPosChangedMessage). > * Fixed a crash during app shutdown for certain custom input handling scenarios inside of a ScrollViewer. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): DwmCoreI_ShutdownManipulationCrash). > * Improved diagnosability for Windows AI model initialization and Text Intelligence APIs. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): ModelInitialization_Insights). -> * Fixed an issue in the Windows AI API `GetReadyState` which erroneously returns `AIFeatureReadyState::NotReady` on unsupported Windows OS versions. The API now returns `AIFeatureReadyState::NotSupportedOnCurrentSystem` ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): ModelInitialization_KnownExceptions). +> * Fixed an issue in the Windows AI API `GetReadyState` which erroneously returns `AIFeatureReadyState::NotReady` on unsupported Windows OS versions. The API now returns `AIFeatureReadyState::NotSupportedOnCurrentSystem` ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): ModelInitialization_KnownExceptions). > * Fixed a critical issue where WebView2 crashes in nested or windowless Xaml Islands, blocking React Native for Windows scenarios. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): XamlRoot_FixGetHostWindowInNestedIslands). >
@@ -61,7 +61,7 @@ Released: **January 13, 2026**

> > * Fixed "Class not registered" errors when using Windows ML in self-contained deployments. Developers using self-contained deployment no longer need to register all the Foundation package activatable classes that were used internally. -> * Fixed a crash that occurs during process shutdown after using Windows ML. +> * Fixed a crash that occurs during process shutdown after using Windows ML. > * Improved `FileOpenPicker`/`FileSavePicker` behavior: > * Filter names display correctly when extensions are hidden. For more info, see GitHub issue [#5837](https://github.com/microsoft/WindowsAppSDK/issues/5837). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): StoragePickers_DisplayFileTypeFilterNames) > * Existing files are not truncated on save unless overwritten. For more info, see GitHub issue [#5976](https://github.com/microsoft/WindowsAppSDK/issues/5976). ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): StoragePickers_DoNotTruncateExistingFileOnSave) @@ -95,7 +95,7 @@ Released: **December 8, 2025**

> > **Expanded OS Support** > Windows ML now supports Windows 10 (version 1809 and later) and Windows Server 2019 and later for CPU and GPU workloads with select execution providers. -Learn more: [Supported Execution Providers](/windows/ai/new-windows-ml/supported-execution-providers) +Learn more: [Supported Execution Providers](/windows/ai/new-windows-ml/supported-execution-providers) > **AMD MiGraphX Execution Provider** > Added support for the AMD MiGraphX execution provider, enabling ML workloads on AMD GPUs for the latest Ryzen AI 300-series processors. This provider is currently being flighted in Windows Insider Program channels and is targeted for retail availability by the end of the month. Learn more: [Supported Execution Providers](/windows/ai/new-windows-ml/supported-execution-providers) @@ -125,7 +125,7 @@ Learn more: [Supported Execution Providers](/windows/ai/new-windows-ml/supporte
Bug fixes -> * Fixed a potential crash if OrientedVirtualizingPanel hits an overflow when computing bounds. (RuntimeCompatibilityChange: OrientedVirtualizingPanel_FixBoundsOverflow). +> * Fixed a potential crash if OrientedVirtualizingPanel hits an overflow when computing bounds. ([RuntimeCompatibilityChange](/windows/windows-app-sdk/api/winrt/microsoft.windows.applicationmodel.windowsappruntime.runtimecompatibilityoptions.disabledchanges): OrientedVirtualizingPanel_FixBoundsOverflow). >
@@ -223,7 +223,7 @@ Released: **September 23, 2025**

Known issues > -> - C# developers must manually reference the [System.Numerics.Tensors]() version 9.0.0 or greater NuGet package in order to use the `Microsoft.ML.OnnxRuntime.Tensors`. Without this NuGet package reference, you will experience the following runtime error when calling the `Microsoft.ML.OnnxRuntime.Tensors` APIs: `Could not load file or assembly 'System.Numerics.Tensors, Version=9.0.0.0`. +> - C# developers must manually reference the [System.Numerics.Tensors](https://www.nuget.org/packages/System.Numerics.Tensors) version 9.0.0 or greater NuGet package in order to use the `Microsoft.ML.OnnxRuntime.Tensors`. Without this NuGet package reference, you will experience the following runtime error when calling the `Microsoft.ML.OnnxRuntime.Tensors` APIs: `Could not load file or assembly 'System.Numerics.Tensors, Version=9.0.0.0`. >
@@ -431,6 +431,8 @@ Released: **August 19, 2025**

+
+
Conversation Summary Options > @@ -558,7 +560,7 @@ Released: **July 8, 2025**

> [!IMPORTANT] > The underlying ML models required for these APIs currently require your device to be running the latest Windows 11 Insider Preview Build on the Dev Channel. Additionally, these APIs require your device to be a Copilot+ PC. See [Copilot+ PCs Developer Guide](/windows/ai/npu-devices) to learn more about these devices. APIs will throw an exception when called on devices lacking the necessary support. > -> The Windows App SDK incorporates advanced Windows AI capabilities, enabling developers to seamlessly integrate intelligent features into their applications. These enhancements include local AI functionalities such as responding to incoming prompts, recognizing text within images, describing image contents, extract objects from pictures, and more. +> The Windows App SDK incorporates advanced Windows AI capabilities, enabling developers to seamlessly integrate intelligent features into their applications. These enhancements include local AI functionalities such as responding to incoming prompts, recognizing text within images, describing image contents, extracting objects from pictures, and more. > > For information on responsible development practices utilized during the creation of the Windows AI APIs, which can also be applied when creating AI-assisted features, consult the [Developing Responsible Generative AI Applications and Features on Windows](/windows/ai/rai) guidance. > @@ -625,7 +627,7 @@ Released: **July 8, 2025**

> - Addressed a potential crash in `ApplicationDataProvider::GetStateFolderUris` caused by reentrancy. For more information see [Windows App SDK GitHub Issue #10513](https://github.com/microsoft/Microsoft-UI-XAML/issues/10513) > - Addressed a UI bug where the `TitleBar` displayed incorrect spacing when a short title was used. For more information see [Windows App SDK GitHub Issue #10492](https://github.com/microsoft/Microsoft-UI-XAML/issues/10492) > - Addressed a UI bug where the `CalendarDatePicker` control displayed incorrect icon margins when a long header was set. For more information see [Windows App SDK GitHub Issue #10469](https://github.com/microsoft/Microsoft-UI-XAML/issues/10469) -> - Resolved an issue related to versioning mismatches between WIndowsAppSDK and Windows SDK NuGet packages, which can cause new projects to fail to build out of the box. For more information see [Windows App SDK GitHub Issue #10467](https://github.com/microsoft/Microsoft-UI-XAML/issues/10467) +> - Resolved an issue related to versioning mismatches between WindowsAppSDK and Windows SDK NuGet packages, which can cause new projects to fail to build out of the box. For more information see [Windows App SDK GitHub Issue #10467](https://github.com/microsoft/Microsoft-UI-XAML/issues/10467) > - Addressed a regression where the mouse wheel input was ignored if the "Scroll inactive windows when hovering over them" setting was disabled, making windows appear perpetually inactive. For more information see [Windows App SDK GitHub Issue #10091](https://github.com/microsoft/Microsoft-UI-XAML/issues/10091) > - Addressed a deployment bug where failing to set `$(WindowsPackageType)=MSIX` in the project file prevents the Deployment Manager from being added, causing apps to require admin privileges unexpectedly. For more information see [Windows App SDK GitHub Issue #8182](https://github.com/microsoft/Microsoft-UI-XAML/issues/8182) > @@ -1038,7 +1040,7 @@ Released: **June 12, 2025**

> [!IMPORTANT] > The underlying ML models required for these APIs currently require your device to be running the latest Windows 11 Insider Preview Build on the Dev Channel. Additionally, these APIs require your device to be a Copilot+ PC. See [Copilot+ PCs Developer Guide](/windows/ai/npu-devices) to learn more about these devices. APIs will throw an exception when called on devices lacking the necessary support. > -> The Windows App SDK incorporates advanced Windows AI capabilities, enabling developers to seamlessly integrate intelligent features into their applications. These enhancements include local AI functionalities such as responding to incoming prompts, recognizing text within images, describing image contents, extract objects from pictures, and more. +> The Windows App SDK incorporates advanced Windows AI capabilities, enabling developers to seamlessly integrate intelligent features into their applications. These enhancements include local AI functionalities such as responding to incoming prompts, recognizing text within images, describing image contents, extracting objects from pictures, and more. > > For information on responsible development practices utilized during the creation of the Windows AI APIs, which can also be applied when creating AI-assisted features, consult the [Developing Responsible Generative AI Applications and Features on Windows](/windows/ai/rai) guidance. > @@ -1408,7 +1410,7 @@ Released: **May 16, 2025**

> [!IMPORTANT] > The underlying ML models required for these APIs currently require your device to be running the latest Windows 11 Insider Preview Build on the Dev Channel. Additionally, these APIs require your device to be a Copilot+ PC. See [Copilot+ PCs Developer Guide](/windows/ai/npu-devices) to learn more about these devices. APIs will throw an exception when called on devices lacking the necessary support. > -> The Windows App SDK incorporates advanced Windows AI capabilities, enabling developers to seamlessly integrate intelligent features into their applications. These enhancements include local AI functionalities such as responding to incoming prompts, recognizing text within images, describing image contents, extract objects from pictures, and more. +> The Windows App SDK incorporates advanced Windows AI capabilities, enabling developers to seamlessly integrate intelligent features into their applications. These enhancements include local AI functionalities such as responding to incoming prompts, recognizing text within images, describing image contents, extracting objects from pictures, and more. > > For information on responsible development practices utilized during the creation of the Windows AI APIs, which can also be applied when creating AI-assisted features, consult the [Developing Responsible Generative AI Applications and Features on Windows](/windows/ai/rai) guidance. > diff --git a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-2-0.md b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-2-0.md index 063afc5aec..f7e19207d9 100644 --- a/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-2-0.md +++ b/hub/apps/windows-app-sdk/release-notes/windows-app-sdk-2-0.md @@ -46,7 +46,7 @@ Released: **February 13, 2026**

> * Improved `DeleteIndex` reliability. Sometimes `DeleteIndex` would fail with ERROR_SHARING_VIOLATION. > * Fix for OCR Bounding boxes returning negative values in some edge cases. -> * App Content Search are part of a separate `Microsoft.Windows.Search` package instead of being part of `Microsoft.Windows.AI package`. +> * App Content Search is part of a separate `Microsoft.Windows.Search` package instead of being part of `Microsoft.Windows.AI package`. > * Fix for prefix search not working with short query strings. > > * New APIs and renames based on official API review. @@ -58,7 +58,7 @@ Released: **February 13, 2026**

> * GetContentIndexingStatus -> GetContentItemStatus > * GetMultipleContentIndexingStatus -> GetContentItemStatuses > * GetContentItems -> * AppCOntentIndexListener +> * AppContentIndexListener > * IndexingStatusChanged -> ContentItemStatusChanged > * AppIndexTextQuerySession > * UpdateQuery -> UpdateQueryPhrase @@ -898,7 +898,7 @@ Released: **November 6, 2025**

> - Query results using `AppIndexQuery.GetNextTextMatches` and `AppIndexQuery.GetNextImageMatches` will be null when there are no matches instead of an empty list. > - Image matches using `AppManagedImageQueryMatch.Subregion` based on OCR values may occasionally be inaccurate, particularly when the text is rotated or skewed. > - Image matches using `AppManagedImageQueryMatch.Subregion` may sometimes include zero-size or extremely small rectangles, leading to inaccurate results. -> - An Empty query from `AppContentIndex.CreateQuery` can throw an exception. +> - An Empty query from `AppContentIndexer.CreateQuery` can throw an exception. >