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
The new look of NuGet gallery added badges for the various frameworks in the packages listing, which is great.
Just that it's missing the badge for .NET nanoFramework... 馃槈 Currently it's defaulting to .NET Framework.
The Elevator Pitch
.NET nanoFramework has been assigned a TFM some time ago. Support for it has been added to nuget CLI. So it seems kind of logical that there is a label for it.
We only support the three major generations as a top-level badge(.NET Framework, .NET Core, .NET). In the future, we will consider adding platforms and more TFMs.
If the asset is under a netnano folder, it should appear in the Frameworks tab. But it will not appear at the top due to what I mentioned above. Double check the contents of the package as we check for assets under specific folders.
Understood. Please add this to the suggestion box as it would be helpful for .NET nanoFramework developers to be able to identify and/or filter NuGet packages that are OK to use in their projects.
Related Problem
The new look of NuGet gallery added badges for the various frameworks in the packages listing, which is great.
Just that it's missing the badge for .NET nanoFramework... 馃槈 Currently it's defaulting to .NET Framework.
The Elevator Pitch
.NET nanoFramework has been assigned a TFM some time ago. Support for it has been added to nuget CLI. So it seems kind of logical that there is a label for it.
Additional Context and Details
TFM: dotnet/designs#208
nuget CLI: NuGet/NuGet.Client#3943 and NuGet/NuGet.Client#4401
The text was updated successfully, but these errors were encountered: