Skip to content
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

Conversation

AaronRobinsonMSFT
Copy link
Member

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 Threads and Tasks.

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

…ined

in the target managed assembly. This allows RegFree COM scenarios and ensures
the intended app manifest is used for the 'exe' scenario.
@AaronRobinsonMSFT AaronRobinsonMSFT added this to the 3.0 milestone Jun 30, 2018
@AaronRobinsonMSFT
Copy link
Member Author

Work found during planning for #18673

Copy link

@luqunl luqunl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AaronRobinsonMSFT AaronRobinsonMSFT merged commit 7222c56 into dotnet:master Jul 2, 2018
@AaronRobinsonMSFT AaronRobinsonMSFT deleted the useAppManifestInDllForCoreRun branch July 2, 2018 23:22
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
…ined (dotnet/coreclr#18728)

in the target managed assembly. This allows RegFree COM scenarios and ensures
the intended app manifest is used for the 'exe' scenario.

Commit migrated from dotnet/coreclr@7222c56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants