It seems to me that it\'s a bad idea to have a domain service require an instance of IOptions to pass it configuration. Now I\'ve got pull additional (unnecessary?) depend
credit
With this two simple lines in startup.cs inside ConfigureServices you can inject the IOptions value like:
public void ConfigureServices(IServiceCollection services)
{
//...
services.Configure(Configuration.GetSection("AppSettings"));
services.AddScoped(cfg => cfg.GetService>().Value);
}
And then use with:
public MyConnectionResolver(AppSettings appSettings)
{
...
}