Remove Mono.Addins from projects and plugins, Replace with dotnet core supported option#159
Closed
Remove Mono.Addins from projects and plugins, Replace with dotnet core supported option#159
Conversation
added 10 commits
February 12, 2026 22:16
…ependent on the scriptengine so dlls get published together.
…the framework code.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Moving Plugin code to https://github.com/natemcmaster/DotNetCorePlugins/tree/main
This is a simpler approach vs Mono.Addins that also handles dependencies in a more sane way/ Its using AssemblyLoadContext under the hood to manage plugin loading. The framework is also compatible with DI and since thats out future direction this is an enabling change.