JetBrains Rider 2019.1 Help

Working with Run/Debug Configurations

To run or debug your code in JetBrains Rider, you can use numerous run/debug configurations. Each run/debug configuration represents a named set of run/debug startup properties. When you perform run, debug, or test operations with JetBrains Rider, you always start a process based on one of the existing configurations using its parameters.

JetBrains Rider comes with a number of run/debug configuration types for the various running, debugging and testing issues. You can create your own run/debug configurations of specific types.

Each run/debug configuration type has its own default settings. Whenever a new run/debug configuration of the respective type is created, it is based on these default settings.

Temporary run/debug configurations

A temporary run/debug configuration is automatically created every time you run a public static void method from the editor.

To save a temporary configuration as permanent, do one of the following:

  • Select it in the Run/Debug Configurations Dialog and click the Save button on the toolbar.

  • Select it in the run/debug configuration selector and then click Save '[configuration name]' configuration.

JetBrains Rider: Saving temporary run/debug configuration

Temporary configurations are marked with semi-transparent icons and are managed the same way as the permanent configurations.
By default, 5 temporary run/debug configurations are allowed per solution, so when you create the sixth configuration the one created first is removed, and so on. To change this limit, use the Temporary configurations limit field in the Templates page of the Run/Debug Configurations Dialog.

Run/debug configuration templates

The templates with default run/debug configuration settings are listed in the Run/Debug Configurations dialog under the Templates node. They denote the settings that are used when new run/debug configurations are created.

You can set the default settings for a specific configuration type that will become applicable to any run/debug configuration of this type created later. Changing defaults does not affect the existing run/debug configurations.

The process of editing per-type default configuration settings is described in Changing Run/Debug Configuration Templates. The process of creating or editing custom run/debug configurations is described in Creating and Editing Run/Debug Configurations.

Last modified: 26 June 2019