Extension method calls provided by a class not in scope of the usings does not have an option to automatically add the required using directive

[vsfeedback]

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

---

For context, I have converted a class full of static methods and properties into a static class full of extension methods using the existing syntax (e.g. public string GetSomeComputedValue(this IConfiguration config) - not the new extension syntax. I am in the process of updating the calling code to call the extension method properly; I get a red squiggly line with an error advising that the extension method cannot be found, suggesting that I am missing a using directive.

When pressing [Ctrl]+[.] to access the available options, it only includes "Invert If". I expect it to recognise that the extension method is in a particular namespace and suggest adding the relevant using directive. It is annoying to have to scroll all the way to the top of the file and manually type in the using directive, especially when CoPilot automatically adds the required using directives when cutting/copying & pasting code between classes.

I seem to recall that Visual Studio 2019 would have this relevant menu item.

---

Original Comments

Feedback Bot on 12/10/2025, 00:10 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Feedback Bot on 1/6/2026, 01:25 PM:

This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.

[litoj]

I thought I had a bug with my completion not working and then I found out it is the lsp that actually doesn't provide the completion.

[litoj]

The problem with extension methods seems to be that their usage visibility is just one-way when they're used outside the csproj where they were defined.

This means when you manually add everything, it lets you be, but it doesn't track the references in a different csproj, so renaming will work only on the csproj, where they were defined.

That is even if you are renaming on a reference from a different csproj directly, it will still rename all references of the csproj with the definition and leave even the reference under the cursor unchanged. That is really confusing and super unhelpful, since there is no way to rename all the usecases in any other csproj, requiring you to go and rename every single reference manually.