Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Searching for NuGet packages in solution explorer no longer works #9505

Closed
zivkan opened this issue Jul 17, 2024 · 2 comments
Closed

Searching for NuGet packages in solution explorer no longer works #9505

zivkan opened this issue Jul 17, 2024 · 2 comments

Comments

@zivkan
Copy link
Member

zivkan commented Jul 17, 2024

Visual Studio Version

I tested 17.10 GA, 17.11 public preview, and internal preview channels. None worked for me today.

Summary

Previously, after enabling "search external files" in Solution Exolorer's search options, it was possible to search for a NuGet package name and it would show any results under the Dependencies node. That's how the screenshots in #9494 were taken.

Steps to Reproduce

  1. Create any SDK style project
  2. Add a package reference to a package that has dependencies. For example, NuGet.Commands
  3. Enable "Search external files" in Solution Explorer's search options
  4. Expand the Dependencies node, and find a dependency of that package you installed. For example, Newtonsoft.Json
  5. Enter that transitive package ID in the Solution Explorer search

Expected Behavior

It shows results, as can be seen in #9494

Actual Behavior

No results found.

User Impact

The NuGet team is documenting this as a way that customers can find why a transitive package is being used by their project.

@drewnoakes
Copy link
Member

@zivkan isn't this a dupe of NuGet/Home#13619? If so, it was fixed recently.

@zivkan
Copy link
Member Author

zivkan commented Jul 17, 2024

Oops, in my stress of trying to meet a few deadlines, I forgot that issue/PR exists! Looks like there was a delay in getting it inserted into VS, which is why Int Preview doesn't have the fix yet.

@zivkan zivkan closed this as completed Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants