Navigation and search

This command, available with Ctrl+T, combines two different features:

Go to Everything, which appears first, provides quick navigation to all possible destinations (types, symbols or files). The list of suggestions appears as soon as you invoke the command and initially includes files and code locations you've recently navigated to. As you type, the list is updated according to your input. You can use special inline commands that start with / for advanced filtering of search results.

Go to Type, which appears when you press the shortcut again, allows you to navigate to any type within your solution.

These and other ‘Go to’ features also support wildcards: * (asterisk) represents zero or more characters; double quotes around the search query will execute an exact match search; ? (question mark) in an exact match search represents a single character once;

This navigation feature, available with Ctrl+F12 shortcut, lets you jump from a base type or member to any of its end implementations, bypassing intermediate steps in the inheritance chain.

It works similar to Go to Derived Symbols but saves you time when you need to bypass one or more levels in a type hierarchy. Watch the GIF to see the difference.

This feature, available by pressing Ctrl+Alt+F7, can take you to any file that is referenced from the current file in one way or another. This is most useful for web sites and applications: for example, it enables you to jump from a web form to its master page, user controls or referenced images. In ASP.NET MVC applications, this feature simplifies navigation from views to controllers and back.

To learn more about advanced navigation and other features that ReSharper makes available to web developers, see ASP.NET and ASP.NET MVC Tools.

Any solution contains both its own source code and references to libraries. We thought it would be great if you were able to navigate to and within those libraries just like you do with the source code.

Some companies publish parts of their sources using the Source Server feature of debug information files (PDB). On the other hand, Microsoft uses this technology to provide access to the source code of the .NET Framework. If you have PDBs available and ReSharper installed, you can access sources stored that way as if they are a part of your solution. If you want to find out what a certain .NET Framework class contains, ReSharper will show it to you as well.

Even if the source server is not available, no worries: ReSharper is able to reconstruct the structure of library code from metadata.

Here's how it works when a source server is available:

1. You click Alt+` on a library symbol to open Navigate To with the list of navigation options.
2. You select an external navigation option for a library symbol.
3. ReSharper downloads PDB files from a source server.
4. ReSharper displays the selected library symbol declaration as if it is defined in your solution.

Find Usages quickly locates usages of any symbol (type, method, field, etc.) in your code. Just position the caret on the symbol for which you want to find usages and press Shift+F12. If you have a mixed-language project, usages can be found across multiple languages with ReSharper.

Search results are displayed in the Find Results window, and organized in a hierarchy. From this window you can directly navigate to any usage with either keyboard or mouse. Additional functionality of Find Results provides several ways to work with search results, including:

• source code preview
• highlighting of broken or unfinished usages
• filtering by read or write usages, invocation usages, attribute usages, usages in documentation, and more criteria
• grouping by type of usage and by categories
• tabs of recent usage searches, and more.

You can navigate between usages, when the Find Results window is open, by pressing Ctrl+Alt+PageUp/PageDown (even from the editor).

To specify the search scope and the type of usages to be found, use the Find Usages Advanced feature available by pressing Ctrl+Shift+Alt+F12.

Depending on the context, you will be able to specify exactly the scope of search in your solution; whether or not to search in referenced libraries; whether to look for textual occurrences, implementing properties or even dynamic references to the symbol you're looking at.

File Structure window is available for all supported languages and file types, In C# or VB.NET files, you can see what methods, fields, classes, and regions they contain, as well as navigate directly to their declarations — just press Ctrl+Alt+F.

In ASP.NET, File Structure lets you examine tags, scriptlets, controls, and other structural elements of a currently opened file, and navigate directly to their declarations. See ASP.NET and ASP.NET MVC Tools for details on how this and other navigation features help web developers.

In build scripts, File Structure lets you see what properties and targets that the current script contains.

The window also lets you rearrange items within the file with a simple drag-and-drop, call navigation actions and refactorings, create and delete regions.

The File Structure window is fully synchronized with the editor. All changes made to a file are immediately reflected in the File Structure and vice-versa.

ReSharper allows using Tab and Shift+Tab keys to jump between logical pieces of your code, similar to how you navigate in your web browser.

For example, when editing a for statement, Tab will select the initializer statement, then the terminating condition and then the iterator statement. Shift+Tab will make these selections in reverse order.

When the cursor sits before the first non-whitespace character in a line, you can still use Tab for indentation.

Learn more: how ReSharper makes Tab great again

With the Intermediate Language Viewer, you can both drill down third-party library code, and display IL that corresponds to your own source code (note you'd have to compile first).

To check out how IL Viewer works, choose ReSharper | Windows | IL Viewer from the menu.

You can quickly navigate to symbols with few usages (e.g. with a private field) by pressing Shift+Alt+F12. Instead of opening an entire tool window, it will display usages in a pop-up.

However, if it turns out that the pop-up with the list of symbol usages contains too many items, just click the magnifier icon in the top right corner of the pop-up to transfer the list of usages to the Find Results window.

This feature lets you create patterns to search for code smells or legacy code that ReSharper doesn't detect out of the box, and replace them with good code. More than that, to make it easy to remove questionable code on a recurring basis, you can create custom code inspections and set up ReSharper to provide quick-fixes for them.

Building patterns and enforcing good practices has never been this easy. Corporate and team policies, custom frameworks, favorite open source libraries and tools — structured patterns are able to cover them all. As a bonus, you can import and export best patterns to share them with colleagues or move between ReSharper installations.

Recent Edits works a lot like Recent Files, showing you a pop-up window with the list of files and symbols that you have recently modified. If your current editing session has started a while ago, narrow down the list by typing a name of the file you're looking to re-open.

Alternatively, use Go to Last Edit Location Ctrl+Shift+Backspace to quickly position the caret at the most recent location where you changed your code, without displaying a pop-up. Subsequent hits of this shortcut will lead you deeper into your editing history.

To-do Explorer helps you keep track of all your reminder items marked with todo, note and/or bug tags, as well as code locations where NotImplementedException are thrown. To-do Explorer retrieves all such items from all files in your solution, and displays them in a single tool window.

If you use your own markers to make notes in comments to your code, you can configure a custom pattern, and To-do Explorer will find it as well.

The Process Explorer window displays all currently running processes, allows exploring their modules and decompiling those of them that are .NET assemblies.

You can choose to show or hide native processes and modules, or turn on process hierarchy view.

Filter the list to find a module or process that you're looking for, and then add its assemblies to Assembly Explorer for further investigation.