Confirm you've already contributed to this project or that you sponsor it
Describe the solution you'd like
OpenIddict currently offers .NET Standard 2.0/2.1 TFMs for most its projects. Both OpenIddict.Client.SystemIntegration and OpenIddict also offer a uap10.0.17763 TFM.
As highlighted by Visual Studio 2026, UWP on .NET Native is being phased out as UWP apps can now target .NET 10 and run on Native AOT, which greatly improves the story for UWP/WinUI 2.x developers. As such, the need for a uap10.0.17763 target in OpenIddict is no longer necessary, as UWP apps converted to the new .NET Native model can directly use the net10.0-windows10.0.17763 build instead.
Once uap10.0.17763 is removed, the netstandard2.0 and netstandard2.1 builds will become practically useless, which is why I'm considering removing the netstandard2.0 and netstandard2.1 TFMs from all the OpenIddict packages, including all the metapackages, the packages containing the EF 6/EF Core/MongoDB models and the OpenIddict.Abstractions package. Doing that will simplify the build infrastructure and the dependencies graph, as we'll no longer need to reference BouncyCastle on any TFM (it's currently used when referencing .NET Framework 4.6.2 and .NET Standard 2.0 but the net462 TFM will be removed in the next OpenIddict version: #2452).
If you have real-world scenarios that require targeting netstandard2.0 or netstandard2.1 (instead of say, net48 or net10.0), I'd love to hear them.
If no real-world scenario requires keeping the netstandard2.0 or netstandard2.1 builds, they'll be removed in 8.0.
Additional context
No response
Confirm you've already contributed to this project or that you sponsor it
Describe the solution you'd like
OpenIddict currently offers .NET Standard 2.0/2.1 TFMs for most its projects. Both
OpenIddict.Client.SystemIntegrationandOpenIddictalso offer auap10.0.17763TFM.As highlighted by Visual Studio 2026, UWP on .NET Native is being phased out as UWP apps can now target .NET 10 and run on Native AOT, which greatly improves the story for UWP/WinUI 2.x developers. As such, the need for a
uap10.0.17763target in OpenIddict is no longer necessary, as UWP apps converted to the new .NET Native model can directly use thenet10.0-windows10.0.17763build instead.Once
uap10.0.17763is removed, thenetstandard2.0andnetstandard2.1builds will become practically useless, which is why I'm considering removing thenetstandard2.0andnetstandard2.1TFMs from all the OpenIddict packages, including all the metapackages, the packages containing the EF 6/EF Core/MongoDB models and theOpenIddict.Abstractionspackage. Doing that will simplify the build infrastructure and the dependencies graph, as we'll no longer need to reference BouncyCastle on any TFM (it's currently used when referencing .NET Framework 4.6.2 and .NET Standard 2.0 but thenet462TFM will be removed in the next OpenIddict version: #2452).If you have real-world scenarios that require targeting
netstandard2.0ornetstandard2.1(instead of say,net48ornet10.0), I'd love to hear them.If no real-world scenario requires keeping the
netstandard2.0ornetstandard2.1builds, they'll be removed in 8.0.Additional context
No response