Better way to get application services from within a derived DbContext instance

I am trying to get a service from within a derived DbContext using the following code:

((IInfrastructure<IServiceProvider>)this).GetService<IMyService>();

The IMyService was previously registered in ConfigureServices in the Startup class. However, the call returns null. I am assuming this is because EF creates a service scope.

My question is how can I get a service that was registered in the Startup class from within a derived DbContext instance. Or, if that makes more sense, how do I register a service in EF’s service scope.

[kevinchalet]

@ajcvickers IMHO, not being able to access the application services from EF code is really annoying, as it makes a bunch of scenarios really hard to implement. For instance, you can’t create a IModelCustomizer that relies on a service defined in Startup.ConfigureServices, as EF uses its own internal service provider.

@ajcvickers was there a particular reason not to make the application service provider accessible from EF’s infrastructure stuff?

[ajcvickers]

@PinpointTownes This is the usual way to replace the internal service provider for ASP.NET apps:

services
    .AddEntityFrameworkInMemoryDatabase()
    .AddDbContext<MyContext>((p, b) => b
        .UseInMemoryDatabase()
        .UseInternalServiceProvider(p));

With regards to ReplaceService, EF has no knowledge of the application service provider unless it passed to EF using UseInternalServiceProvider.