Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore NuGet version 7.0.x does not support NET 6.0.x, but the EntityFrameworkCore 7.0.x does support NET 6.0.x.

[bakgerman]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

May be related to Issue 45278

This NuGet package Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore version 7.0.x only supports NET 7.0

But...
Microsoft.Extensions.Diagnostics.HealthChecks 7.0.x supports NET Standard 2.0, 4.6.2, and 7.0
Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions 7.0.x supports NET Standard 2.0, and 4.6.2
Microsoft.EntityFrameworkCore.* 7.0.x supports NET 6.0

Describe the solution you'd like

If the item being health checked, EntityFrameworkCore 7.0.x, supports NET 6.0, and the 2 NuGet packages for Microsoft.Extensions.Diagnostics.HealthChecks listed above support 6.0 by supporting Standard 2.0, then shouldn't this package support NET 6, instead of just NET 7.0?

I have EntityFrameworkCore 7.0.x working fine on NET 6.0, and using HealthChecks NuGets 6.0.x.
And it works fine, but I should really be able to update the Hea;lthChecks NuGets to 7.0.x
When I update Microsoft.Extensions.Diagnostics.HealthChecks and Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions to 7.0.x and have to leave Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore on 6.0.x I get a run time exception.

Additional context

No response

[ajcvickers]

@javiercn I don't think we own this. It is shipped out of the ASP.NET Core repo: https://github.com/dotnet/aspnetcore/tree/main/src/Middleware/HealthChecks.EntityFrameworkCore

[adityamandaleeka]

Moving to web-frameworks since it's health checks.

[rafikiassumani-msft]

@bakgerman Unfortunately we do not support this at the moment and making the changes will require a lot of work. Would you be able to upgrade your runtime to 7.0.x ?

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.