You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just saw the .NET Standard Deep Dive
video with @richlander and @terrajobst, and I think it would be handy if all ~70% of NuGet packages that are API compatible with .NET Standard 2.0, were market on http://nuget.org.
For instance, if I navigate to the https://www.nuget.org/packages/NQuery/ page, I want to see the NQuery NuGet is compatible with .NET Standard 2.0. Probably, the easiest way would be, add a special tag (not editable for a package's owner), which will also help to filter by a different criteria.
From @Petermarcu on September 5, 2017 15:28
Copied from here: dotnet/standard#477
from @olegburov
I just saw the .NET Standard Deep Dive
video with @richlander and @terrajobst, and I think it would be handy if all ~70% of NuGet packages that are API compatible with .NET Standard 2.0, were market on http://nuget.org.
For instance, if I navigate to the https://www.nuget.org/packages/NQuery/ page, I want to see the NQuery NuGet is compatible with .NET Standard 2.0. Probably, the easiest way would be, add a special tag (not editable for a package's owner), which will also help to filter by a different criteria.
from: @tpetrina
Not only that, show the structure of nupkg file. This way we can at least analyse /lib folder to see which targets it supports.
Copied from original issue: NuGet/Home#5845
The text was updated successfully, but these errors were encountered: