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.
Default run/debug configuration settings
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.