Last modified: 31 October 2023

note

Rider's debugger does not support the following types of applications:

• Single-file applications — applications that were built with the /p:PublishSingleFile=true flag.

• Native applications that host CLR to run .NET code. For example, applications that use CLR Hosting.

Debugger is an integral part of JetBrains Rider that allows you to examine the runtime behavior of your application, identify problematic code, and isolate the source of the problem step by step.

Typical debugging steps

1. Define a run/debug configuration for the program that you want to debug.

2. Set breakpoints in the source code where the potential problem may lie.

3. Start debugging by launching your program in the debug mode AltF5 or attaching to a running process CtrlAlt0P.

4. When the program execution breaks, step through your code, inspect variables, and evaluate expressions.

5. You can edit the code of a suspended program and then continue debugging without restarting with Hot Reload.

6. Resume the debugging session F5 to let the program run to the next breakpoint, if any.

7. To finish the debugging session, press ShiftF5, select Run | Stop in the menu, or click Stop in the Debug window.

The major part of debugging activities takes place in the Debug window, which becomes available once you start debugging. To open this window, press Alt05 or select View | Tool Windows | Debug in the main menu.

While debugging, you can also perform the most common debugger actions from the AltEnter menu. For example Run to Cursor, Skip to Cursor or Toggle breakpoints:

Gif

You may be also interested in the following language- and framework-specific guidelines:

• Debug JavaScript in Chrome

• Running and debugging TypeScript

• Running and debugging Node.js

• Debug Unity Applications