Debugger

If this checkbox is selected, you can click a line number in the editor to run program execution to this line.

Select how you want to remove breakpoints:

• By clicking them with the left mouse button

• By dragging them to the editor or clicking them with the middle mouse button. In this case, clicking a breakpoint will toggle its state between enabled and disabled.

You can also choose whether you want a confirmation dialog to be displayed when you are about to remove a conditional or a logging breakpoint

This checkbox only affects files of non-.NET languages (for example, JavaScript or TypeScript files).
In .NET languages, you can edit and continue, which is controlled with the Enable Edit And Continue checkbox below on this page.

The checkbox is disabled by default because when you edit code in the debug mode, it is no longer synchronized with the debugger and can lead to unexpected results.
If Show prompt to allow editing is enabled, you will be able to edit files after accepting a warning that appears on each edit attempt. Otherwise, editing of files of non-.NET languages will be blocked when you are in the debug mode.

When this option is on, you can edit your code and continue debugging without restarting.

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.

When this option is on, all your changes made in the debug session will be applied before the debugger makes the next step or resumes the program. Therefore, the debugging session could be broken, for example if your changes lead to a build failure.
This approach is similar to Visual Studio debugger. Although your changes can break the debugging session, it makes sure that the code in the editor is synchronized with the debugger at each step.

If this option is off, your changes will not be synchronized with the debugger on step or resume, instead, you will be able to apply the changes explicitly with the corresponding action.
This approach is similar to the Hot Swap in Java debuggers. It lets you continue debugging regardless of your changes, and it works well when your changes do not affect the code you are currently stepping over.

Use this checkbox to automatically refresh expressions that include functions calls in watches.

When the checkbox is enabled, all watches will be refreshed automatically, but complex expressions with function calls could negatively affect debugger performance and can also lead to unexpected changes in the program state.

When the checkbox is disabled, simple variables and expressions will be refreshed automatically anyway, and you will be able to refresh complex expressions with an explicit action when necessary.

• not handled within the code of the current solution

• handled in external code

• thrown either in the code of the current solution or in external code, but always have code of the current solution in the call stack

• thrown in external code

• handled in external code

• have no code of the current solution in the call stack

This set of options lets you configure the default just-in-time (JIT) debugger for your system. You can see the current JIT debuggers for 32 bit and 64 bit process and use the buttons to set JetBrains Rider as the default debugger or restore the one which was set default previously.

When JetBrains Rider is set as the default JIT debugger and a process calls Debugger.Launch, you will see a dialog that helps you choose how to start the debugger. (1) If the solution with the application source code is open, you can pick it from the list of opened solutions.
Alternatively, you can choose a JetBrains Rider installation. In this case, debugger will start in an empty solution, and you will be able to debug decompiled code of the process. An additional checkbox allows you to remember the selected option (2), in which case for every future attempt, the debugger will be attached automatically:

Use this spin box to specify the port on which the built-in web server runs. By default this port is set to port 63342 through which JetBrains Rider accepts connections from services. You can set the port number to any other value starting with 1024 and higher.

For security reasons, any request to a page on the built-in server from outside JetBrains Rider is by default rejected and the authorization popup is displayed.

To access the requested page, click Copy authorization URL to clipboard and paste the generated token in the address bar of the browser.

However this behavior may be annoying, for example, it may block your debugging session if manual intervention is impossible. To suppress displaying the authorization popup, select the Allow unsigned requests checkbox.