Run/Debug Configuration: .NET Project
|Project:|| Choose a startup project for this configuration. |
Note that only projects of executable types (e.g. Console Application) could be selected here.
If you want to run a non-executable project (e.g. Class Library), use the .NET Executable configuration and choose an executable that will run your project.
|Target framework:||A .NET Framework version that will be used to run this configuration.|
|Exe path:||The path to the executable file of the selected target project is calculated automatically, but you can change it if needed.|
|Program arguments:|| Arguments that will be passed to the executable when the configuration is started. |
For some project types (e.g. Web Application), JetBrains Rider will fill this field automatically so that the target project could be started correctly.
|Working directory:||The working directory is automatically set to the bin/Debug path of the selected target project, but you can change it if needed.|
|Environmental variables:||Here you can specify custom environment variables for the target executable.|
|Runtime variables:|| Both dotnet and Mono support setting custom runtime arguments when launching an application. For example Mono supports many runtime arguments to customize how your application is run. You can select the garbage collector to be used (|
|Use mono runtime|| If you are working on Windows, you can check how your application works with the mono runtime. JetBrains Rider will use the mono executable specified on the page of JetBrains Rider settings (Ctrl+Alt+S). |
To debug with mono runtime, you need:
|Use external console:|| By default, the output of .NET Core and Mono applications is shown in the Run or Debug window. Use this check box to show the output in an external window. |
This check box does not affect classic .NET application types (e.g. .NET Console Application) — their output in always shown in an external window.
Browser / Live Edit tab
In this tab, configure the behaviour of the browser and enable debugging the client-side code of the application. This functionality is provided through a
|Open browser||In the text box in this area, specify a project HTML file to create a correct URL to this file according to the project root to be started on the built-in web server. For example, if you choose project_root/inner_folder/index.html the resulting URL will be http://localhost:63342/project_root/inner_folder/index.html. If you select the After Launch check box, the browser will open this page automatically after the application starts. Alternatively you can view the same result by opening the page with this URL address in the browser of your choice manually.|
|After launch|| Select this check box Choose the browser to use from the drop-down list next to the After launch checkbox. |
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
|Name||In this text box, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example. from the Run popup (Ctrl+Shift+Alt+R).|
|Share|| Select this check box to make the run/debug configuration available to other team members. |
The shared run/debug configurations are kept in separate xml files under
|Single instance only|| |
If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, JetBrains Rider checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your solution as well as adjust default configurations templates.
|Ctrl+N||Create a run/debug configuration.|
|Ctrl+R, D||Delete the selected run/debug configuration. Note that you cannot delete default configurations.|
|Ctrl+D||Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.|
|Edit Templates||View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations.|
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
|Move into new folder / Create new folder|| |
You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag-and-drop or and buttons.
To remove grouping, select a folder and click .
|Sort configurations||Click this button to sort configurations in the alphabetical order.|
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
|Configurations available in Run Dashboard|| |
In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display the configuration types for which you have created one ore more configurations.
|Confirm rerun with process termination||The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration. |
|Temporary configurations limit||Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
Before Launch options
In this area you can specify tasks that must be be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
|Ctrl+N|| Click this icon to add one of the following available tasks: |
|Ctrl+R, D||Click this icon to remove the selected task from the list.|
|Enter||Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.|
|/||Alt+Up/Alt+Down||Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)|
|Show this page||Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.|
|Activate tool window|| |
Otherwise, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.