❔ Strategy for plugin architecture dependency injection

I am creating an application with simple plugins in which registration information of plugins are stored in a database. I am having challenges with dependency injection. Each plugin assembly has the following marker assembly:

 csharp
public interface IPluginRegistrar
{
    IServiceCollection RegisterPluginServices(IServiceCollection services);
}

 csharp
public interface IPluginRegistrar
{
    IServiceCollection RegisterPluginServices(IServiceCollection services);
}

Idea is to call the interface above for each of plugin assemblies stored in the database, but I cannot resolve my plugin

DbContext

DbContext

without doing

BuildServiceProvider()

BuildServiceProvider()

which I cannot do(or not advised to do) during

ConfigureServices()

ConfigureServices()

. Is there any strategy or pattern to tackle this?

C#•3y ago•

32 replies

pirrippu

❔ Strategy for plugin architecture dependency injection

 csharp
public interface IPluginRegistrar
{
    IServiceCollection RegisterPluginServices(IServiceCollection services);
}

 csharp
public interface IPluginRegistrar
{
    IServiceCollection RegisterPluginServices(IServiceCollection services);
}

Idea is to call the interface above for each of plugin assemblies stored in the database, but I cannot resolve my plugin

DbContext

DbContext

without doing

BuildServiceProvider()

BuildServiceProvider()

which I cannot do(or not advised to do) during

ConfigureServices()

ConfigureServices()

. Is there any strategy or pattern to tackle this?

❔ Strategy for plugin architecture dependency injection

Similar Threads

❔ Strategy for plugin architecture dependency injection

Similar Threads

Similar Threads

Similar Threads