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.|
|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. |
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 the URL address to open the application at. 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 to have a browser started automatically after a debugging session is launched. Specify the browser to use in the drop-down list next to the check box. |
Before Launch options
Specify which tasks should be carried out before starting the run/debug configuration.
|Ctrl+N|| Click this icon to add a task to the list. Select the task to be added, for example: |
|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 check box to show the run/debug configuration settings prior to actually starting the run/debug configuration.|
|Activate tool window|
|Ctrl+N||Create a run/debug configuration.|
|Ctrl+R, D||Delete the selected run/debug configuration.|
|Ctrl+D||Create a copy of the selected run/debug configuration.|
|View and edit the default settings for the selected run/debug configuration.|
|Alt+Up/Alt+Down||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 in the corresponding list on the main toolbar.
|You can group run/debug configurations by placing them into folders. |
To create a folder, select the configurations to be grouped and click . Specify the name of the folder.
Then, to move a configuration into a folder, between the folders or out of a folder, use and . You can also drag a configuration into a folder.
To remove grouping, select a folder and click .