On October 1st, the NuGet team enabled Target Framework Filtering in NuGet.org's Search API. We're happy to announce we've just flipped the switch in our back-end to enable this on MyGet feeds as well! Ever since version 2.1, the NuGet clients have been sending the consuming project's target framework in the search requests. Everyone who's using NuGet 2.1 or above is going to benefit from this server-side optimization.
What does this mean for you as a package consumer?
Since NuGet will now be filtering package search results by target framework, in a nutshell, you should no longer see this dialog when installing packages:
More details about this feature can be found on the NuGet blog.
I'm using upstream package sources. Does anything change?
Yes and no. Upstream package sources that support target framework filtering, like NuGet.org and MyGet.org, may return different (but better) results from what was returned previously. For other package sources, we will return search results the way we did before.
If the clients were sending this information to the server since v2.1, what took you so long?
We want MyGet feeds to be fully compatible with the NuGet API that lives at www.nuget.org. This means we want MyGet to provide a consistent behavior from a user/client perspective.