Skip to content

Gallery should show which frameworks a package is compatible with #4843

@terrajobst

Description

@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:

image

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:

image

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:

image

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?

image

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions