This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Set the activation context for the CoreRun application #18728
Merged
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.
to what is defined in the target managed assembly. This allows RegFree COM scenarios and ensures
the intended app manifest is used in the 'exe' scenario. The set activation context becomes the default for all subsequent threads and since at this point no other threads exist, this approach in hosting works. I have verified the context is properly inherited by new managed
Thread
s andTask
s.This approach addresses some of the issues related to app.manifests in hosting scenarios. See core-setup#4314 and sdk#1899.
cc @ericstj @luqunl @jkotas