Question 1

How do I load MVC controllers from a plugin in ASP.NET Core using DotNetCorePlugins?

Accepted Answer

Install the McMaster.NETCore.Plugins.Mvc package and use the .AddPluginFromAssemblyFile() method in Startup.ConfigureServices. This allows the MVC framework to discover controllers and views from the specified plugin assembly. Check the samples/aspnetcore-mvc directory for working examples.

Question 2

What are shared types in DotNetCorePlugins and why are they important?

Accepted Answer

Shared types are specified when creating a PluginLoader to ensure certain types, like interfaces, are unified across plugin boundaries. This prevents type casting issues and allows objects to be passed safely between host and plugins. The README includes diagrams to illustrate this concept.

Question 3

DotNetCorePlugins vs the built-in System.Runtime.Loader: which should I use?

Accepted Answer

Use DotNetCorePlugins if you need advanced features like fine-grained type sharing, hot reload, or support for .NET Core 2. For simpler scenarios, the built-in APIs from .NET Core 3+ might suffice, but they lack the convenience and control offered by this library, as noted in the README.

Question 4

How can I unload a plugin at runtime with DotNetCorePlugins?

Accepted Answer

Set the isUnloadable parameter to true when creating the PluginLoader. Ensure all references to types from the plugin are cleaned up, then call the loader's Unload method. This enables hot reload functionality for dynamic updates without app restarts.

Question 5

Can I use DotNetCorePlugins with .NET Framework or older .NET Core versions?

Accepted Answer

Version 2.0+ of DotNetCorePlugins only supports .NET 8. For older .NET versions, you need to use version 1.*, which may have limited features and updates. Refer to the NuGet package details for compatibility information.

Question 6

How do I handle dependencies in plugins to avoid conflicts?

Accepted Answer

DotNetCorePlugins isolates each plugin's dependencies by loading them into separate AssemblyLoadContexts. Publish each plugin into its own directory to prevent file contention, and use shared types only for necessary interfaces to maintain isolation, as described in the getting started guide.

DotNetCorePlugins

What is DotNetCorePlugins?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions