Use assembly loading context to isolate loaded assemblies from AppDomain #714 #715
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.
See issue #714
I was running into issues running Mapster.Tool against projects with .NET 9 preview assemblies references (either directly or transitively from other dependencies.)
After sleuthing through dotnet/runtime CLR code I ran into this issue which seemed pertinent:
dotnet/runtime#102981
This PR is based off of recommendations by @jkotas there about how to load assemblies in an isolated way. It appears to have solved my issue with Mapster.Tool 8.4.1-pre01 mentioned.