Gallery should show which frameworks a package is compatible with

[terrajobst]

The NuGet web site (and client UI) doesn't really show which frameworks a package is compatible with. Instead, it renders the dependency groups. If there are no dependency groups, it doesn't show any frameworks:

And if there are some, it quickly looks super busy, even in packages with few dependencies (check out JSON.NET). And for meta packages it's basically not working at all (check out NETStandard.Library).

If think we want to render the lowest version of a framework that the package is compatible with. We probably also want to hide or at least deemphasize legacy frameworks:

If my package only targets .NET Standard, I should still see the list of frameworks I’m effectively compatible with (i.e. the list above). Ideally, the list of frameworks would remain the same between packages but we’d indicate unsupported ones. For instance, let’s say the package only targets .NET Framework 2.0, this is what I would expect to see:

Logically, I think we want to have a list of frameworks on the server for which we do hit testing with each package. Adding new frameworks should update the display for all packages.

.NET Standard

We probably want to treat .NET Standard specially, at least by displaying it first. If a package has .NET Framework assets, it might be consumable via the .NET Standard 2.0 compatibility mode. It seems we should think if and how we could render that information. Maybe like this?

[jbogard]

What would this look like for packages that multi-target different versions of the same TFN? JSON.NET for example has separate versions for:

• net20
• net35
• net40
• net45
• netstandard1.0
• netstandard1.3
• PCL junk drawer

Would it just show ".NET Framework 2.0 (or higher)"? A few of my packages also include additional features depending on what .NET Standard version you're on, so I'll multi-target accordingly.

[adamralph]

#2787, #2805, #4077, #4598, ...

[terrajobst]

@adamralph

Fair point. So far, I've not seen any concrete proposals for a design, though.

[terrajobst]

@jbogard

Yeah, I was thinking about that too. I'm wondering if that might be too much information for the person just trying to find what would work. Another option might be icons in front of the framework name that indicates how that platform is supported (indirectly by .NET Standard, or explicitly). Multi targeting across multiple versions could be a toggle in the UI (like [x] Show lowest versions only).

[anangaur]

NuGet/Home#5725

[jamesmontemagno]

Can we make things filterable in the search too?!?!? Would be amazing :)

[DmytroSokhach]

Can we have it implemented like on fuget.org please?

[drewgillies]

Spec: https://github.com/NuGet/Home/blob/dev/accepted/2021/NuGet.orgTFMs.md

[adelarsq]

@JonDouglas Would also possible to add Fable on the list?

[JonDouglas]

@adelarsq This is out of scope right now as this work has already been merged and will be released shortly. I encourage you to create a separate issue regarding the feature request.

[adelarsq]

@JonDouglas Nice! Thanks for the reply. I will create a new request for this.

[JonDouglas]

https://devblogs.microsoft.com/nuget/introducing-compatible-frameworks-on-nuget-org/

🚢🚢🚢 (Thanks to @dannyjdev, @jcjiang & team!)