Bug 18972 - The extension method's parent class is not visible in the list of code suggestions
Summary: The extension method's parent class is not visible in the list of code sugges...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.2.3
Hardware: Macintosh Mac OS
: Low enhancement
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2014-04-12 17:27 UTC by Ievgen
Modified: 2017-07-19 20:58 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

The solution with a code to demonstrate the problem is attached (413.27 KB, application/zip)
2014-04-12 17:27 UTC, Ievgen

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Ievgen 2014-04-12 17:27:04 UTC
Created attachment 6563 [details]
The solution with a code to demonstrate the problem is attached

The solution with code sample is attached. Open the class ExtensionNamespaceNotFound for details.

If there is a static class with an extension method somewhere in the solution the class name isn't visible in the list of code suggestions shown on Ctrl+Alt+Space click. So you can't import it easy and you have to spend some time looking for a class namespace in the solution.

This feature works fine by default in Vistua Studio ReSharper.
Comment 1 Mike Krüger 2014-04-24 05:21:04 UTC
You're right that's a missing feature in the ctrl+alt+space import symbols.

That's because I always do it like:  


(If you've source analysis enabled it works with command+return)

I'll rework the import symbols feature soon (at least this year :)) - I add the extension methods there as well.
Comment 2 Ievgen 2014-04-24 13:38:16 UTC
Oh, well, thanks for a good advise! I haven't even noticed that "Resolve" item in the Context Menu (who would? :-)). It will be definitely easier to import some basic namespaces like "System.Linq" when using the most common extensions like First(), Any() etc. (although interaction with a mouse required...)

Still looking forward to the refactoring of symbols that you're about to start! Thanks.
Comment 3 Mike Krüger 2014-04-24 13:41:01 UTC
You can use alt+return or command+return on mac :)
Comment 4 Tom Opgenorth 2017-07-19 20:58:36 UTC
Looks like this is not an issue with Visual Studio for Mac v7.1 Preview.