[NuGet.org Bug]: search by tfm doesn't find non-latest versions of packages that are compatible

[zivkan]

Impact

It's more difficult to complete my work

Describe the bug

A customer recently reported a problem to Visual Studio roughly related to package compatibility with their project: https://developercommunity.visualstudio.com/t/NuGet-package-update-of-MicrosoftBuild-/10782347

I remembered that nuget.org's website has TFM filtering, so I thought I'd give it a go, but I found that it does not work in a way that this customer would have wanted.

The customer wants to find versions of a package that is compatible with their project, even if it's not the latest version of the package

Repro Steps

Search for packageid:Microsoft.Build.

See the search result for version 17.12.6 is compatible with .NET Framework 4.7.2 and .NET 9.

In the search filter, select .NET 8 and click apply. see that now it claims there are no packages

Expected Behavior

The search results should return package version 17.11.4, which is compatible with .NET 8

Screenshots

No response

Additional Context and logs

No response

[zivkan]

Here are two more related issues reported to the client team:

• NuGet package manager does not respect selected "FrameworkVersion" on Update in Package manager UI Home#13926
• Version Range support in UI and PMC update Home#6566

The issue titles might not sound like an exact match of this issue's title, but if you read the comments, several customers are reporting experiences where this issue would be the ideal solution.