Confirm you've already contributed to this project or that you sponsor it
Describe the solution you'd like
Earlier today, the ASP.NET team announced that ASP.NET Core 2.3 and Entity Framework Core 2.3 will no longer be supported after April 2027: aspnet/Announcements#529, meaning neither ASP.NET Core nor EF Core will be supported on .NET Framework after that date.
The OpenIddict.Client.AspNetCore, OpenIddict.Client.DataProtection, OpenIddict.Server.AspNetCore, OpenIddict.Server.DataProtection, OpenIddict.Validation.AspNetCore and OpenIddict.Validation.DataProtection packages all reference ASP.NET Core 2.3 for the .NET Framework TFM. Similarly, the OpenIddict.EntityFrameworkCore package references EF Core 2.3 as the minimal version when targeting .NET Standard 2.0 and .NET Framework.
I know a few companies are still using OpenIddict on ASP.NET Core 2.3 (due to third-party dependencies that are not supported on .NET Core, typically) but it's not clear how many OpenIddict users exactly will end up behind affected. If you still use OpenIddict on ASP.NET Core 2.3 or with Entity Framework Core 2.3, please add your voice here.
Additional context
Should the outcome of this thread indicate that supporting ASP.NET Core 2.3 is no longer useful, the following changes will be made next year:
- The
OpenIddict.Client.AspNetCore, OpenIddict.Server.AspNetCore and OpenIddict.Validation.AspNetCore packages will no longer target .NET Framework. The OpenIddict.AspNetCore metapackage will also be updated accordingly.
- The
OpenIddict.Client.DataProtection, OpenIddict.Server.DataProtection and OpenIddict.Validation.DataProtection packages will reference Microsoft.AspNetCore.DataProtection version 10.0 when targeting .NET Framework. This dependency still offers a .NET Framework TFM, so we should still be able to use it in .NET Framework apps.
- The
OpenIddict.EntityFrameworkCore package will no longer offer a .NET Framework target framework moniker.
- All the OpenIddict packages will use
Microsoft.Extensions.* 10.0 as the minimum version.
Note: there's no plan to stop targeting .NET Framework in the other projects and the OpenIddict OWIN integrations (typically used in ASP.NET 4.6.2+ apps) will still be fully supported after April 2027, independently of the outcome of this thread. Similarly, OpenIddict.Client.SystemIntegration will still target .NET Framework. That said, it's possible .NET Framework 4.7.2 will become the new minimum .NET Framework version supported by OpenIddict, since .NET Framework 4.6.2 will stop being supported by Microsoft in January 2027.
Confirm you've already contributed to this project or that you sponsor it
Describe the solution you'd like
Earlier today, the ASP.NET team announced that ASP.NET Core 2.3 and Entity Framework Core 2.3 will no longer be supported after April 2027: aspnet/Announcements#529, meaning neither ASP.NET Core nor EF Core will be supported on .NET Framework after that date.
The
OpenIddict.Client.AspNetCore,OpenIddict.Client.DataProtection,OpenIddict.Server.AspNetCore,OpenIddict.Server.DataProtection,OpenIddict.Validation.AspNetCoreandOpenIddict.Validation.DataProtectionpackages all reference ASP.NET Core 2.3 for the .NET Framework TFM. Similarly, theOpenIddict.EntityFrameworkCorepackage references EF Core 2.3 as the minimal version when targeting .NET Standard 2.0 and .NET Framework.I know a few companies are still using OpenIddict on ASP.NET Core 2.3 (due to third-party dependencies that are not supported on .NET Core, typically) but it's not clear how many OpenIddict users exactly will end up behind affected. If you still use OpenIddict on ASP.NET Core 2.3 or with Entity Framework Core 2.3, please add your voice here.
Additional context
Should the outcome of this thread indicate that supporting ASP.NET Core 2.3 is no longer useful, the following changes will be made next year:
OpenIddict.Client.AspNetCore,OpenIddict.Server.AspNetCoreandOpenIddict.Validation.AspNetCorepackages will no longer target .NET Framework. TheOpenIddict.AspNetCoremetapackage will also be updated accordingly.OpenIddict.Client.DataProtection,OpenIddict.Server.DataProtectionandOpenIddict.Validation.DataProtectionpackages will referenceMicrosoft.AspNetCore.DataProtectionversion 10.0 when targeting .NET Framework. This dependency still offers a .NET Framework TFM, so we should still be able to use it in .NET Framework apps.OpenIddict.EntityFrameworkCorepackage will no longer offer a .NET Framework target framework moniker.Microsoft.Extensions.*10.0 as the minimum version.Note: there's no plan to stop targeting .NET Framework in the other projects and the OpenIddict OWIN integrations (typically used in ASP.NET 4.6.2+ apps) will still be fully supported after April 2027, independently of the outcome of this thread. Similarly,
OpenIddict.Client.SystemIntegrationwill still target .NET Framework. That said, it's possible .NET Framework 4.7.2 will become the new minimum .NET Framework version supported by OpenIddict, since .NET Framework 4.6.2 will stop being supported by Microsoft in January 2027.