Package discovery: Show and search by TFM/package-compatibility

[hickford]

A feature request: I'd like to browse packages compatible with .NET Core

Most the packages on https://www.nuget.org/packages seem not to be, so it would be useful to shortlist those that are

>dotnet restore
Package Microsoft.Net.Http 2.2.29 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). 
One or more packages are incompatible with .NETCoreApp,Version=v1.0.

I want to search nuget.org by target framework.

Recently Triaged Issues

All issues in this section should be triaged by the v-team into one of their business objectives or features.

• Create an Engineering Spec for Phase 1 of Search-by-TFM #8863
• Prototype adding asset frameworks from the catalog in Catalog2AzureSearch #8864
• Prototype including Computed Frameworks in the supportedFrameworks search index field #8865

It is extremely necessary that we have a separate list for .NET Core compatible packages to allow ease of use.

[praveenksharma]

It is a must. Please implement it in some way. I wasted so much time today figuring out which dapper version is dotnet core and which is not.

[feliwir]

Yea I can't really work with nuget without that feature

[skofman1]

@harikmenon ?

[jdehaan]

Not only for .Net core but add tags for all supported platforms. It seems to me this could be easily done just after the upload during the package registration process in the db by looking at the folders present inside the lib/ folder. Having that info in the db, allows then adding a feature in the gallery to allow filtering per tags. Really looking forward to having that great feature!

[lgreenlee]

Yes - this is an issue. Visually browsing I cannot see if packages are compatible with .NET Core, thus it is impossible to select the right packages to install without actually attempting the install. It would also be nice in applications that use NuGet, if they could also filter by target runtime. Frequently versions are shown that cannot be restored on a .NET Core platform.

[adamralph]

Issues #3098 (this one), #2936 and #2787 all seem to be using different words to talk about the same feature.

[poimis]

"compatible with .NET Core" is not the right wording for this issue as there are many cores already. We need to be able to search by target tfm, I.E. "gimme packages compatible with .NET Standard 1.4". Or "gimme packages compatible with PCL profile111" etc.

[nbarbettini]

Agreed, being able to do advanced filtering by TFMs would be great.

[anavarro9731]

Agreed, completely

[mrnickel]

I really believe it would be a boon to the .net community if this were implemented.

By way of an example:

Just today I wanted to replace an "old" piece of Java software I had written to run on .NET core (C#). This piece of technology CURRENTLY has a dependency on Beanstalkd. It would have been VERY helpful for me to be able to limit my search on Nuget.org for packages that were compatible with core.

[karann-msft]

@anangaur

[msollicito]

I agree - its almost impossible to program to .net core because this does not exist