Repository navigation
Bump the nuget-minor-and-patch group with 1 update - #59
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Microsoft.WindowsAppSDK from 2.0.1 to 2.6.4 --- updated-dependencies: - dependency-name: Microsoft.WindowsAppSDK dependency-version: 2.6.4 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
|
TokenBurn AI review complete. 0 findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Microsoft.WindowsAppSDK from 2.0.1 to 2.6.4.
Release notes
Sourced from Microsoft.WindowsAppSDK's releases.
2.6.4
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:
Bug fixes:
TextBoxorRichEditBox, was still alive while the XAML core was being torn down.AppInstance.GetInstancescould fail withE_INVALIDARGwhile enumerating application instances.AppNotificationManagerandAppInstanceAPIs.Microsoft.WindowsAppRuntime.Insights.Resource.dllwhen using theVersionInfoAPIs or registering anAppNotificationcallback (microsoft/WindowsAppSDK#6071, microsoft/WindowsAppSDK#6387).DispatcherQueuecallback could produce a crash dump with only the HRESULT, omitting the app's original exception type, message, and stack trace.DispatcherQueueTimer.Tickevent handlers.ContentIslandor other Content object immediately terminated the app. The original error is now returned to the calling code instead.Windows.UI.Compositionobjects intoMicrosoft.UI.Composition, preserving object identity, when using the System Composition Engine.ItemsViewwhen the target ofStartBringItemIntoViewwas collapsed or recycled before the scroll completed (microsoft/microsoft-ui-xaml#11865).WebView2control received focus while still initializing and its parent window was temporarily disabled when initialization finished.InitializeComponentandx:Namefields, in WinUI 3 C# projects edited in VS Code with C# Dev Kit. To opt out, set theEnableWinUIDesignTimeGeneratedXamlCompileItemsproperty tofalse.To see everything that's new and changed, see the full Windows App SDK 2.6.4 release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.5.4-exp
Windows App SDK 2.5 Experimental is the latest experimental release, adding new Windows AI capabilities, code-based theme resource bindings and
DataTemplateconstruction, the newTableViewandChartcontrols, and expanded WinUI 3 inking support. It follows Windows App SDK 2.5.1 stable and brings forward the changes from that release alongside the experimental-only additions below.What's new in WinAppSDK 2.5 Experimental:
AIComputeDeviceAPIs let apps choose the default, CPU, or NPU execution device for text recognition. App Content Index image indexing can use the same preference for OCR throughContentRegionImageOptions.PreferredTextRecognizerDevice.FrameworkElement.SetThemeResourceBindingAPI lets apps create the equivalent of a{ThemeResource}binding programmatically.DataTemplateconstruction. A new experimentalDataTemplateconstructor accepts an app-provided delegate that creates the template's element subtree.TableViewcontrol. The experimentalTableViewcontrol is now available in the public WinMDs, with grouping, templated group headers, sorting and filtering, resizable columns, and optional cell and header tooltips.Chartcontrol. A new experimental WinUI 3Chartcontrol presents Cartesian data as line, area, and bar series, with configurable axes, legends, labels, and markers.InkPresenter.ActivateCustomDryingandInkSynchronizerAPIs let apps render committed ink themselves, andInkToolbarnow targets anInkPresenterdirectly.Bugs fixed:
InkPresenter.StrokeContainerwhile custom drying was active.InkCanvaspresenter sizing under aRenderTransform.To see everything that's new and changed, see the full Windows App SDK 2.5 Experimental release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.5.1
Windows App SDK 2.5.1 adds Windows Error Reporting support for self-contained .NET MSIX apps, introduces limited-access app content search APIs, and includes reliability fixes across WinUI 3, input, composition, deployment, and Windows AI.
What's new in WinAppSDK 2.5.1:
windows.diagnosticServiceModulepackage-manifest extension to declare diagnostic modules, allowing Windows Error Reporting to load them and collect actionable crash dumps.AppContentIndexAPIs to index text and images, perform lexical queries, and use semantic matching on supported NPU-enabled devices. The APIs support semantic search and retrieval-augmented generation scenarios.Bug fixes:
NavigationViewwhen resizing the control could produce a negative paneMaxHeight.ElementCompositionPreview.GetPointerPositionPropertySetstopped updating while a pointer was pressed.NavigationViewwhen an expanded item's flyout was shown after the item had been collapsed or recycled.KeyboardAcceleratorused an OEM or punctuation key and displayed the accelerator shortcut label.CommandBarwith no secondary commands could show an empty overflow button at fractional display scales such as 175%.VisualInteractionSource.CreateFromIVisualElement.SceneLightingrendering for apps using the System Composition Engine.InputPointerSource.ActivationBehaviornot honoringNoActivatewhen using the System Composition Engine.CompositionEngineselection behavior for null inputs and no-op selections.ICompositionObjectqueries on gradient stop collections when using the System Composition Engine.ContentExternalOutputLinkborder and background behavior when using the System Composition Engine.VisualReferenceControllerwhen using the System Composition Engine.To see everything that's new and changed, see the full Windows App SDK 2.5.1 release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.4.1-exp
Windows App SDK 2.4 Experimental (2.4.1-experimental) 🧪
Windows App SDK 2.4 Experimental is the latest experimental release, headlined by inking support for WinUI 3. It follows Windows App SDK 2.4.0 stable and generally brings forward the changes from that release alongside the experimental-only addition below.
What's new in WinAppSDK 2.4 Experimental:
InkCanvas,InkToolbar, andInkPresenterAPIs add pen and touch input, clipboard and high-contrast support, stroke input, and unprocessed input to WinUI 3 apps.To see everything that's new and changed, see the full Windows App SDK 2.4 Experimental release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.4.0
Windows App SDK 2.4.0
Windows App SDK 2.4.0 is the latest stable release on the 2.x line, adding expanded input support, more precise
LanguageModelresponse statuses, and targeted reliability fixes across input, Storage Pickers, MRT Core, app runtime isolation, composition, and XAML tooling.What's new in WinAppSDK 2.4.0:
Windows.Devices.Haptics, along with touchpad single-finger panning, when supported by the operating system and hardware.LanguageModelresponse statuses. The newLanguageModelResponseStatus.UnsupportedLanguageandLanguageModelResponseStatus.LanguageMismatchvalues let apps distinguish unsupported-language and input/output-language mismatch conditions from generic errors.Bug fixes:
MrmGetFilePathFromNamereturnedERROR_FILE_NOT_FOUNDwhen the PRI file didn't exist instead of returning the documented fallback path. See GitHub issue microsoft/WindowsAppSDK#5940.MICROSOFT_WINDOWSAPPRUNTIME_BASE_DIRECTORYcould be inherited by child processes, disrupting MRT Core and catalog lookups. See GitHub issue microsoft/WindowsAppSDK#5987.VisualInteractionSource.TryRedirectForManipulation.DISABLE_XAML_GENERATED_MAINis defined. See GitHub issue microsoft/microsoft-ui-xaml#11245.To see everything that's new and changed, see the full Windows App SDK 2.4.0 release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.3.2-expA
Windows App SDK 2.3 Experimental A (2.3.2-experimentalA) 🧪
Windows App SDK 2.3 Experimental A is the latest experimental release, headlined by new DPI-aware window sizing from XAML, a substantial round of App Content Index indexing and reliability improvements, and additional Windows AI and speech APIs. It builds on the Windows App SDK 2.3.1 stable release and adds the experimental-only work described below.
What's new in WinAppSDK 2.3 Experimental A:
Window.WidthandWindow.Height. New properties give apps a DPI-aware way to get and set a window's size in logical (client) pixels directly from code or markup, without reaching throughWindow.AppWindowand doing manual logical-to-physical DPI conversion. CompanionWindow.MinWidth,Window.MinHeight,Window.MaxWidth, andWindow.MaxHeightproperties constrain the window's size.AppContentIndexer.BatchAddOrUpdate, direct indexing of bitmap and image-stream content (with OCR and semantic options), static ranking boosts for individual content items or regions, ICU-based multilingual tokenization, and automatic recovery from index corruption. Indexing and query paths are also substantially faster, with more stable lexical ranking.LanguageModel.GenerateStructuredJsonResponseAsyncAPI lets apps generate structured JSON output from the on-device language model, making it easier to get typed, machine-readable results back from a prompt.SpeechAudioProvidernow implementsIClosable, so apps can deterministically release the provider withClose/Disposewhen they finish streaming audio.To see everything that's new and changed, see the full Windows App SDK 2.3 Experimental A release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.3.1
Windows App SDK 2.3.1
Windows App SDK 2.3.1 is the latest stable release on the 2.x line, with a new structured JSON output API for Phi Silica, the
XamlOptionalChangesAPI for opting into XAML breaking changes, an unstableCompositionEngineLimited Access Feature, Video Super Resolution improvements, ARM64EC support for Windows ML, a broad set of XAML performance optimizations, and a batch of reliability fixes.What's new in WinAppSDK 2.3.1:
LanguageModel.GenerateStructuredJsonResponseAsyncAPI generates language-model responses constrained to a caller-supplied JSON Schema, so apps get well-formed, schema-conformant output instead of free-form text they have to parse themselves.XamlOptionalChanges. A new API that lets apps opt into optional breaking changes before XAML initialization. In the same release, theDISABLE_XAML_GENERATED_MAINpreprocessor constant now renames the generatedmain()method (C#:XamlGeneratedProgram.XamlGeneratedMain(); C++/WinRT:wXamlGeneratedMain()) instead of removing it, so a custommain()can invoke the default implementation. See PR microsoft/microsoft-ui-xaml#11110.CompositionEngine(Limited Access Feature). A new, unstable Limited Access Feature that lets apps opt into using the OS as the engine for the Composition APIs.DefaultStyleOptimizationsandOptimizeApplyStylesXamlChangeIds, including optimizedXamlControlsResourcesstyles, a lighterFontIcon/BitmapIconvisual tree, and fasterThemeResourceandResourceDictionarylookups.Microsoft.WindowsAppSDK.AINuGet package.Bug fixes:
ApplicationData.GetForUnpackaged().LocalSettings()opening a registry key at a roaming path (HKCU\SOFTWARE\publisher\product) instead of a machine-local one, so unpackaged app settings now persist in the correct location. See GitHub issue microsoft/WindowsAppSDK#6559.backgroundTaskHost.exewhen a background task had no stored CLSID, and added graceful handling whenCoCreateInstancefails. See GitHub issue microsoft/WindowsAppSDK#5870.MediaPlayerPresenterwhen the GPU device is lost during media playback event handling.CPopupRoot::ReplayPointerUpdatewhen a popup is closed synchronously during pointer-event replay.LayoutStatedereference) inUniformGridLayoutandFlowLayoutthat could occur when a collection change was raised on anItemsRepeaterthat was no longer loaded.To see everything that's new and changed, see the full Windows App SDK 2.3.1 release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.2.2-exp9
Windows App SDK 2.2 Experimental 9 (2.2.2-experimental9) 🧪
Windows App SDK 2.2 Experimental 9 is the latest experimental release. It ships alongside Windows App SDK 2.2.0 stable and generally brings over the changes from that release; the highlights below describe the experimental-only additions.
What's new in WinAppSDK 2.2 Experimental 9:
EnsureReadyAsyncthrough Windows Update. Apps should checkGetReadyStateand display a consent dialog before triggering the download. Users can manage the model at Settings > System > AI Components. For responsible AI guidance, see the new Transparency Note: Language Model APIs on Non-Copilot+ PCs.Microsoft.Windows.AI.Speechenable both batch and streaming speech-to-text.BatchRecognitionrecognizes a complete audio source in a single call, andStreamingRecognitionraisesRecognizingandRecognizedevents. Audio can be sourced from a device (AudioConfiguration.FromAudioDevice), file (FromFile), input stream (FromStream), or pushed by the caller viaSpeechAudioProvider(16 kHz, 16-bit, single-channel PCM). The on-device model is managed viaSpeechRecognitionModel.EnsureReadyAsync/TryCreateAsync, with download and load progress reported throughSpeechRecognitionModelProgress.NpuTypeAPI. A newMicrosoft.Windows.Workloads.NpuTypeenum surfaces the NPU class on the current device (for example,Qnn,Lnl,Stx,Win365,Unknown,None), so apps and Workloads infrastructure can route AI workloads to the appropriate execution path.This release also rolls forward all changes from the 2.2.0 stable release: the new
Microsoft.Windows.AI.Video.VideoScalerVideo Super Resolution API, the newMicrosoft.Windows.Storage.ApplicationData.GetForUnpackaged()entry point for unpackaged apps, the newXamlBindingHelperboxing-free setter overloads, and the WinUI / Windows ML reliability fixes shipped in 2.2.0.New or updated APIs (since 2.1 Experimental 8):
Microsoft.UI.Xaml
Microsoft.UI.Xaml.Markup
Microsoft.Windows.AI.Video
Microsoft.Windows.Storage
... (truncated)
2.1.4-exp8
Windows App SDK 2.1.4-Experimental8 (2.1.4-experimental8) 🧪
Windows App SDK 2.1 Experimental 8 ships alongside Windows App SDK 2.1.3 stable. It generally brings forward the changes in 2.1.3 (TitleBar custom drag-region APIs, the Phi Silica LoRA API on the stable surface,
AICapabilities.HasAICapability, expanded Windows ML execution-provider support, ONNX Runtime 1.24.6, and the 2.1.3 bug fix batch) and adds one experimental-only refinement to the Phi Silica structured JSON output API.What's new in WinAppSDK 2.1 Experimental 8:
LanguageModelExperimental.GenerateStructuredJsonResponseAsync(introduced in 2.0 Experimental 7) now returns a dedicatedGenerateStructuredJsonResponseResulttype with aGenerateStructuredJsonResponseStatusproperty, instead of the genericLanguageModelResponseResult/LanguageModelResponseStatuspair. The new status enum is specific to schema-constrained generation: it includes aResponseInvalidJsonvalue for cases where the model output did not satisfy the requested JSON schema, separate from generic language-model response failures.ResponseInvalidJsonvalue has been removed from the stableLanguageModelResponseStatusenum. Apps that handledResponseInvalidJsonfromLanguageModelResponseStatusshould move that handling onto the newGenerateStructuredJsonResponseStatusreturned byGenerateStructuredJsonResponseAsync.Brought forward from 2.1.3 stable
This experimental release also rolls forward the 2.1.3 stable changes, including the new TitleBar custom drag-region APIs, the Phi Silica LoRA API on the stable surface,
AICapabilities.HasAICapability, the Windows ML execution-provider improvements, the ONNX Runtime 1.24.6 bump, and the full 2.1.3 bug fix batch. See the Windows App SDK 2.1.3 release notes for details.To see everything that's new and changed, see the full Windows App SDK 2.1 Experimental 8 release notes.
Try it out
Getting Started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
2.1.3
Windows App SDK 2.1.3
Windows App SDK 2.1.3 is the latest stable servicing release on the 2.x line, with new TitleBar drag-region APIs in WinUI, the LoRA API for Phi Silica promoted to the stable surface, a new Copilot+ PC detection API, expanded Windows ML execution-provider support, an ONNX Runtime update, and a batch of reliability fixes.
What's new in WinAppSDK 2.1.3:
TitleBarnow recursively walksTitleBar.Contentand automatically excludes interactive controls from the drag region while keeping empty gaps draggable by default. Three new APIs (TitleBar.IsDragRegionattached property,TitleBar.AutoRefreshDragRegions, andTitleBar.RecomputeDragRegions()) give developers explicit control when the default behavior isn't sufficient. See PR microsoft/microsoft-ui-xaml#10936 and tracking issue microsoft/microsoft-ui-xaml#10421.LanguageModelLowRankAdapter.CreateFromPathandLanguageModelOptions.LowRankAdapter. See Phi Silica LoRA for details.Bug fixes:
ItemsRepeaterwhere recycled elements were never garbage collected due to a reference cycle through theRecyclePool, which could also cause crashes inInvalidateChildrenMeasure.CUIElement, causing an access violation. The callback now uses a weak reference to safely handle the case where the element is destroyed before the animation completes.OverrideScale, causing content to appear oversized and clipped. See GitHub issue microsoft/microsoft-ui-xaml#11000.UIAffinityReleaseQueue::DoCleanup.GetModuleHandleWhas been replaced withGetModuleHandleExWso the correct module is resolved by address.UniformGridLayout::GetMajorSizewhen anItemsRepeateris laid out in an available width narrower than one item's minor stride.GetReadyStatecould return incorrect error codes (for example,DisabledByUserorNotSupportedOnCurrentSystem) when required packages were not yet deployed. The API now correctly reportsNotReadyin this scenario, improving diagnostic clarity.dotnet build, showing onlyMSB3073: exited with code 1instead of the actual error messages. See GitHub issue microsoft/microsoft-ui-xaml#9813.To see everything that's new and changed, see the full Windows App SDK 2.1.3 release notes.
Try it out
Getting started
To get started using Windows App SDK to develop Windows apps, check out the following documentation:
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions