dotnet / roslyn

The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.
https://docs.microsoft.com/dotnet/csharp/roslyn-sdk/
MIT License
19.02k stars 4.03k forks source link

"Find All References" does not find all the associated references of namespaces #74718

Open vsfeedback opened 2 months ago

vsfeedback commented 2 months ago

This issue has been moved from a ticket on Developer Community.


[severity:I’m unable to use this version]
As you can see in the attached screenshot - “Find All References” only found “usings” of a given namespace, but “ClippingUtility” class that is defined under that namespace, as well as some other classes - are not present in the search.
This is a critical issue for my workflow.

upd: This bug is only present in "Project Then Definition" grouping, as far as I observe. "Project then Containing Type" for example - does not produce such issue.


Original Comments

Feedback Bot on 8/8/2024, 10:10 PM:

(private comment, text removed)

Alessio T on 8/10/2024, 10:14 AM:

(private comment, text removed)

Sam Harwell on 8/12/2024, 09:18 AM:

Hi Alessio T,

Can you file a separate issue for your feedback. The current issue is only being handled by the C# language team, and I have no way in the tooling to redirect a comment within the larger issue over to the C++ team.

Thank you,
Sam Harwell


Original Solutions

(no solutions)

CyrusNajmabadi commented 2 months ago

It's unclear what the issue is here. The picture the user showed seems reasonable:

Image

LVNov commented 2 months ago

Hello,

According to the given example, the file "ClippingUtility.cs" does not appear in the search results, even though it belongs to the "Game.Utilities.Client" namespace and the search was conducted using the "Utilities" component of the namespace. It is expected that all files within the "Game.Utilities" scope or that use the "Game.Utilities" namespace should be displayed. Otherwise, I don't understand the logic behind the search.

CyrusNajmabadi commented 2 months ago

@LVNov Gotcha. Thanks for the clarification!