Navigation and Search
dotPeek enables you to find your way through the source code using the declarations, members, method calls, inheritance hierarchy, and so on.
The scope of navigation and search includes all assemblies currently loaded in the Assembly Explorer window and all assemblies referenced from those assemblies. See Navigating Compiled Code to learn how the navigation is performed within compiled assemblies.
Navigation and search commands are available in themenu, with keyboard shortcuts, as well as in the context menu of the code viewer and other windows.
Depending on your task, different sets of dotPeek's navigation and search features may help you:
If you need to find anything in your solution or referenced libraries by name, study the commands in the Navigation by Name section.
If you need to go to any items related to the current code symbol, study the commands in the Navigation from Symbols section.
dotPeek also provides a general-purpose Navigate To shortcut that groups all navigation options available from the current caret position. To learn more about this shortcut, see Navigate To section.
If you want to find usages of a particular symbol in the current file, project, solution, or referenced libraries, study the commands in the Finding Usages section.
Depending on the current caret position in the editor, dotPeek can suggest a lot of relevant navigation options. To learn more about these options, see Context Navigation.
If you need to find any text in the current document, use the Quick Find window.
dotPeek supports the Go to Line command that brings you to a specific line in the current document.
Besides, dotPeek provides other means of navigation:
For types and interfaces that are overridden and implemented elsewhere, for methods implementing, overriding or hiding other methods, dotPeek shows gutter icons that provide quick navigation up and down the inheritance hierarchy:
For more information, see Go to Base Symbols and Go to Derived Symbols.
The Stack Trace Explorer window, which enables you to navigate from a stack trace to the error location in the source code, and thus pinpoint the malfunction. For more information, see Navigating from Stack Trace to Exception.