Fix MSIX bundle crashes when publishing with trimming enabled #2
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 publishing a .NET application as an MSIX bundle with trimming enabled (
PublishTrimmed=true), the application crashes with aMissingMethodExceptionstating thatSystem.Environment.SetEnvironmentVariablemethod could not be found. This occurs because the .NET trimmer removes this method, which is used by the Windows App SDK initialization code.Changes
Modified
UndockedRegFreeWinRT-AutoInitializer.csto handle the case whenEnvironment.SetEnvironmentVariableis trimmed away:AppContext.SetDatawhich is less likely to be trimmedAdded documentation in the FAQ to explain the issue and solution:
Testing
The changes have been designed to handle both scenarios:
Environment.SetEnvironmentVariableis available)AppContext.SetDataas fallback)These changes maintain backward compatibility while adding support for trimmed applications.
Fixes #1.
💡 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.