Update DynamicAssembly usage to honor different AssemblyLoadContext's #1978
Conversation
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
BertanAygun
pushed a commit
to BertanAygun/MessagePack-CSharp
that referenced
this pull request
Apr 9, 2025
…sue1952 Update DynamicAssembly usage to honor different AssemblyLoadContext's
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change resolves issue #1952 where dynamic resolvers did not work where same assembly in different locations was loaded in different AssemblyLoadContext's.
DynamicAssembly creation now happens per unique AssemblyLoadContext so that types are recognized correctly.