ReSharper Web Help

ReSharper | Navigate | Go to Symbol

The Go To Symbol is the most far-reaching of the "Go to" family of search commands; it allows solution-wide search by name for any code symbol.

To navigate to a symbol
  1. On the main menu, choose ReSharper | Navigate | Go to Symbol , or press Ctrl+Shift+Alt+N.
  2. In the Enter symbol name pop-up that appears, start typing characters in the text field. As you type, the lookup list narrows down, suggesting names that match the entered substring.
  3. By default, only symbols from the solution display in the lookup list. If needed, you can select the Include library types check box or press Alt+N to display symbols from libraries, referenced in the solution.
  4. Do one of the following:
    • To view the list of found symbols in the Find Results window, click Show in Find Results in the lookup list or press + on the numeric keypad.
    • To navigate directly to a symbol, select the symbol in the lookup list and press Enter.

 Note

If the target symbol belongs to the current solution, ReSharper will open the corresponding file in the editor and set the caret at the type declaration. If the symbol is found in referenced libraries, ReSharper navigates according to the settings defined in the External Sources page of the ReSharper options. For more information, see Navigating to Compiled Code.

Case-insensitive CamelHumps is supported here: for example, you can simply type 'ch' instead of 'ColorHelper'. If you want to navigate to a symbol in a particular type, you can specify parts of the type's fully qualified name and member name and split them with spaces or dots. Consider the example below:

You can also use wildcards when specifying the name: '*' (asterisk) represents zero or more characters; '+' (plus) represents one or more characters; '?' (question mark) represents one or zero characters.

 Note

Whenever collecting items to match the specified string takes significant time, ReSharper displays an hourglass icon to the right of your search string. Substantial delays are to be expected when performing search before ReSharper loads completely.

See Also

Procedures