[Feature]: Please highlight EOL .NET versions

[richlander]

Related Problem

Compatible frameworks are displayed as all equal. We choose to highlight targets that happen to be included in the package. We should highlight (or lowlight) targets that are EOL.

• https://www.nuget.org/packages/Microsoft.Extensions.Logging/9.0.0-preview.1.24080.9#supportedframeworks-body-tab
• https://www.nuget.org/packages/NuGet.Packaging#supportedframeworks-body-tab

The Nuget.Packaging package make this problem particularly obvious. The highlighted .NET version is an EOL one. That's very odd.

The Elevator Pitch

Make it easier for customers to know that their usage might be concerning.

Additional Context and Details

#9835

[ericstj]

I'm not sure if it's best for this issue or not, but the support table can be improved in more ways.

Today it's completely calculated. Calculation is good since it will help predict what NuGet behavior will be, but it doesn't allow for a package to control that.

Sometimes a package might add a targets file specifically to say it's not supported somewhere. Ideally there would be a way to represent that in this gallery UI. Today since the package would install there it looks like it's supported which is the opposite of what we'd want.

Another case is a package that wants to represent that it's no longer needed on a framework. We don't have the ability for frameworks to represent this, but maybe the package could - at least in this visualization.

[richlander]

Great topic. Do you have an example package that demonstrates that use case?

[erdembayar]

cc @JonDouglas