ReSharper 2017.2 Help

Navigating from Stack Trace to Exception

ReSharper | Tools | Browse Stack Trace
Ctrl+Shift+E
ReSharper_ExploreStackTrace

When you receive an external stack trace (for example, from a bug report), you can open it in the Stack Trace Explorer window and navigate to code where the corresponding exception originated. In the stack trace, files, types, and methods are displayed as hyperlinks. You can click them to display the corresponding items in the editor.

To navigate to code that caused an exception

  1. Copy exception stack trace to the clipboard.
  2. By default, if you copy a stack trace that contains symbols from the currently opened solution and then switch focus to Visual Studio, ReSharper will automatically load it to the Stack Trace Explorer window and bring it to the view. If you do not like this behavior, clear the Auto open external Stack Traces check box on the Tools | Stack Trace Explorer page of ReSharper options. If the auto opening is disabled, use the shortcut or menu command as described below.
  3. In the main menu, choose ReSharper | Tools | Browse Stack Trace , or press Ctrl+Shift+E. The Stack Trace Explorer window opens, displaying the exception stack trace from the clipboard in a new tab.
  4. In the Stack Trace Explorer window, click highlighted items to display the corresponding code in the editor.
  5. If you prefer to wrap long lines in the stack trace, use the corresponding toolbar button /help/img/dotnet/2017.2/ThemedIcon.LineBreaks.Screen.[Gray].png or specify the default preference for line wrapping on the Tools | Stack Trace Explorer page of ReSharper options.
Navigating from stack trace to exception
Last modified: 11 September 2017

See Also