Fix resource.pri handling in single file publishing for WindowsAppSDK #10
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.
Issue
When creating a single executable from an unpackaged app with
PublishSingleFile=trueandWindowsAppSDKSelfContained=true, the latest Windows App SDK (1.5.240428000) fails to properly include theresource.prifile in the output. This causes runtime errors when attempting to load resources from the app.Root Cause
In version 1.5 of Windows App SDK, resource files (including
resource.pri) are supposed to be embedded into the executable and extracted to a temporary directory at runtime. However, the required MSBuild properties to ensure this extraction works correctly were not being set when bothPublishSingleFileandWindowsAppSDKSelfContainedwere enabled.Solution
Added the following properties to
Microsoft.WindowsAppSDK.Foundation.targetsto ensure resource files are properly included for self-extraction during single file publishing:These properties ensure that:
IncludeNativeLibrariesForSelfExtract- Native libraries (including MRM.dll which handles resources) are included for self-extractionIncludeAllContentForSelfExtract- All content files (including resource.pri) are included for self-extractionThis fix allows resource files to be properly extracted at runtime from the single file executable, restoring the functionality that was working in Windows App SDK 1.4.
Fixes #9.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
cdn.fwupd.org/usr/bin/fwupdmgr refresh(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.