npgsql ef integration doesn't provide a callback that accepts an IServiceProvider

[aaronpowell]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm porting a codebase to use .NET Aspire and the way that it configures the DbContext is that it uses the callback that takes an IServiceProvider and the options builder: https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.dependencyinjection.entityframeworkservicecollectionextensions.adddbcontext?view=efcore-9.0#microsoft-extensions-dependencyinjection-entityframeworkservicecollectionextensions-adddbcontext-1(microsoft-extensions-dependencyinjection-iservicecollection-system-action((system-iserviceprovider-microsoft-entityframeworkcore-dbcontextoptionsbuilder))-microsoft-extensions-dependencyinjection-servicelifetime-microsoft-extensions-dependencyinjection-servicelifetime)

Aspire doesn't provide access to this, only to the one that takes the DbContextOptionsBuilder, which means that we have to refactor how things are configured.

Expected Behavior

If the Aspire integration is going to "shadow" the native integration, it should match the API surface area.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

No response

[aaronpowell]

This is also a problem with the MySQL integration

[DamianEdwards]

IIUC this is by design. We purposely don't try to provide top-level method overloads for all scenarios when using EF Core. For advanced cases, you should call the standard EF Core method overload you want, and then call EnrichNpgslDbContext to add the Aspire goodness.

/Cc @eerhardt

[eerhardt]

We purposely don't try to provide top-level method overloads for all scenarios when using EF Core.

Correct. See Redesign EF components public API (dotnet/aspire#1403)