fix: launch on 25H2 (installed WASDK 2.4, not self-contained CoreMessagingXP) - #4
Merged
Conversation
Self-contained WASDK 2.4.0 ships CoreMessagingXP 10.0.27200.1048, which fail-fasts (0xC0000602) at the first Window() on Windows 11 25H2. Also give the tray icon a generated glyph so ForceCreate has an IconSource.
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
1 participant
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.
Summary
Window()on Windows 11 25H2 (26200).WindowsAppSDKSelfContainedto false so the app uses the installedMicrosoft.WindowsAppRuntime.22.4.0 package.CommunityToolkit.WinUI7.1.2.Rglyph soForceCreatehas an IconSource.Test plan
dotnet build Reentry.slnx -c Debug -p:Platform=x64Reentry.exestays alive and shows the first-run consent window on FUNCULAR-WKS-02 (25H2)