Open JonDouglas opened 2 years ago
@dannyjdev If OK with you, I'd like to resurrect your old PR and address the peer review comment for the missing null check
The + should always be there. A package targeting net6
is usable in future net*
frameworks.
Similar to netstandard1.1
being usable by something targeting netstandard2.0
etc.
Having a package target multiple frameworks like net6
and net8
just means that there is something different (different dependency versions, different code, etc.) for the net8
support compared to net6
.
@dannyjdev If OK with you, I'd like to resurrect your old PR and address the peer review comment for the missing null check
do it!
The + should always be there. A package targeting
net6
is usable in futurenet*
frameworks. Similar tonetstandard1.1
being usable by something targetingnetstandard2.0
etc.Having a package target multiple frameworks like
net6
andnet8
just means that there is something different (different dependency versions, different code, etc.) for thenet8
support compared tonet6
.
great point!
Related Problem
No response
The Elevator Pitch
If a package supports more than 1 target framework in a specific .NET category, it should include a "+" sign next to it's badge at the top of the package details page.
Example:
Has more than 1 target framework in two different categories and thus should show
.NET Standard 1.0+
and.NET Framework 2.0+
.Additional Context and Details
No response