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
Define a run/debug configuration for the application to be debugged.
Set breakpoints in the source code where the potential problem may lie.
Start a debugging session Alt+F5.
You can also edit your code and continue debugging without restarting. The project will recompile in the background. This works in projects targeting .NET Framework and .NET Core on Windows (except WPF) when Enable Edit And Continue is ticked on the page of JetBrains Rider settings Ctrl+Alt+S.
There are cases when modifying the code is not possible and a restart is required. These include changing signatures, modifying generic functions, renamings of any kind, and some more. If this happens JetBrains Rider will make you aware by showing a tooltip.
Resume the debugging session F5 to let the program run to the next breakpoint, if any.
To finish the debugging session, press Shift+F5, select Stop in the Debug Tool Window. This will detach the debugger from the application and make the application exit (in case you have run it from JetBrains Rider).in the menu, or click
The major part of debugging activities takes place in the Debug Tool Window, which becomes available once you start debugging. To open this window, press Alt+5 or select View | Tool Windows | Debug in the main menu.
You may be also interested in the following language- and framework-specific guidelines:
- Running and debugging TypeScript
- Running and Debugging Node.js
- Debugging Unity Applications