Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Package discovery: Show and search by TFM/package-compatibility
See original GitHub issueA 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.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:138
- Comments:34 (9 by maintainers)
Top Results From Across the Web
NuGet Spring 2018 Roadmap
This feature aims to reduce confusion with NuGet package identity ... Package discovery: Show and search by TFM/package-compatibility NuGet# ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It is extremely necessary that we have a separate list for .NET Core compatible packages to allow ease of use.
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.