Maybe need lazy AddPlugin

[1257960069]

[1257960069]

we must rename the autoquery.cs to ConfigureDbAutoQuery, this will ensure AutoQueryFeature.GenerateCrudServices.DbFactory can get IDbConnectionFactory from asp.net ioc. Modular Startup default order may be is by className.

public class ConfigureDb : IHostingStartup
{
    public void Configure(IWebHostBuilder builder) => builder
        .ConfigureServices((context, services) =>
        {
            var dbFactory = new OrmLiteConnectionFactory("", Provider);
            services.AddSingleton<IDbConnectionFactory>(dbFactory);
//we can get the Singleton instance by  services.Last(s => s.ServiceType == typeof(IDbConnectionFactory)).ImplementationInstance as IDbConnectionFactory
//  services.AddSingleton<IDbConnectionFactory,OrmLiteConnectionFactory>(); this way can not get instance  when building service
        });
}

public class ConfigureDbAutoQuery : IHostingStartup
{
    public void Configure(IWebHostBuilder builder) => builder
       .ConfigureServices((context, services) =>
       {
           var appSettings = new NetCoreAppSettings(context.Configuration);
           services.AddPlugin(new AutoQueryFeature
           {
               MaxLimit = 1000,
               IncludeTotal = true,
               GenerateCrudServices = new GenerateCrudServices
               {
//we must ensure that ConfigureDbAutoQuery.ConfigureServices was called after ConfigureDb.ConfigureServices
                   DbFactory = services.Last(s => s.ServiceType == typeof(IDbConnectionFactory)).ImplementationInstance as IDbConnectionFactory,
                   CreateServices = new List<CreateCrudServices> {
                        new CreateCrudServices()
                        {
                        }
                    }
               },
           });
       });

[mythz]

Lazy wont work since the services need to be generated and dependencies resolved before the IOC is built.

Easiest way is to combine OrmLite and AutoQuery in the same Configuration so you have access to the dbFactory instance.

https://github.com/NetCoreApps/NorthwindAuto/blob/master/Configure.AppHost.cs

Might also be cleaner to get the DbFactory from a singleton instance:

public class ConfigureDb 
{
    public static IDbConnectionFactory? DbFactory { get; set; }

    public void Configure(IWebHostBuilder builder) => builder
        .ConfigureServices((context, services) => {
            DbFactory = new OrmLiteConnectionFactory("", Provider);
            services.AddSingleton<IDbConnectionFactory>(DbFactory);
        });
}

But yeah would need to rename classes to ensure correct order of execution.

[1257960069]

can we register plugins to services?. for exmaple:

AddMyPluginsFeature(this services, Action<MyPluginsOptions>? configure)
{
var options=new MyPluginsOptions();
configure?.invoke(options);
services.AddTransient<IPlugin>(sp=>{  
return new MyPlugin1(sp.GetRequiredService<IDbConnectionFactory>)
{
  xx=options.xx
} 
}); 
services.AddTransient<IPlugin, MyPlugin2>();
}

init plugins in app.UseServiceStack

 var allPlugins=  app.Services.GetRequiredService<IEnumerable<IPlugin>>():
Init(allPlugins);

this will change a lot of code for Plugins.
this is a good way for asp.net core serivces and middleware

[mythz]

That wouldn't solve anything. The generated Services need to be generated before the IOC is built and dependencies can't be resolved before IOC is built so you can't use the IOC to resolve the IDbConnectionFactory dependency, i.e. it needs to be populated and resolved outside of the IOC.

We're not changing how plugins work, since it needs to remain backwards compatible and work when not using ASP .NET Core IOC.