asp.net core with jasper, no longer possible to resolve DbContext

I have an asp.net core app, where jasper is registerd as follows:

public static IWebHost BuildWebHost(string[] args) =>
            WebHost.CreateDefaultBuilder(args)
                .UseStartup<Startup>()
                .UseJasper<JasperConfig>()
                .Build();

JasperConfig doesn’t contain any DI registrations. My regular startup.cs though, contains a registration for dbContext and for IMyService.

 public void ConfigureServices(IServiceCollection services)
        {
            string connectionString = "Server=(localdb)\\mssqllocaldb;Database=etc ....;

            services.AddDbContext<ApplicationDbContext>(options =>
                options.UseSqlServer(connectionString));
            services.AddScoped(typeof(IMyService), typeof(MyService));
            services.AddMvc();
        }

Now, I have an mvc controller with following constructor:

public ValuesController(IMessageContext messageContext, IMyService myService, ApplicationDbContext dbContext)

        {
            _messageContext = messageContext;
            _myService = myService;
            _dbContext = dbContext;
        }

The Jasper messageContext and myService are resolved but dbContext is NOT resolved. When I remove the jasper registration (and remove IMessageContext from constructor) everything works fine.

Any idea what i’m doing ‘wrong’? thx

[jeremydmiller]

Got it.

[jeremydmiller]

Huh, okay then. I’ll take a look over the weekend. Thanks for the repro steps, that should make this quick.