Run/Debug Configuration: .NET Launch Settings Profile
This run/debug configuration type helps you run and debug .NET Core/ASP.NET Core applications that have their launch settings configured in a launchSettings.json file.
What is launchSettings.json
launchSettings.json, which is placed in the Properties folder of a project, describes how the application can be launched — the command to execute, whether the browser should be opened, which environment variables should be set, and so on. This information can then be used by JetBrains Rider, by dotnet run, or by any other tool to run or debug the application.
This article details the conventions used in launchSettings.json. The example below shows a sample launchSettings.json with two launch profiles:
IIS Express and
Creating run/debug configurations based on launchSettings.json
When you open a project with launchSettings.json for the first time, JetBrains Rider will pick the available launch profiles and automatically create corresponding run/debug configurations, which you can then use to run and debug the project.
For example, after cloning and opening the Orchard CMS, JetBrains Rider will create the following run/debug configurations from the launchSettings.json files:
JetBrains Rider only generates run/debug configurations automatically when no user-defined run configurations were created in the solution before. If there are existing run/debug configurations, you can right-click launchSettings.json in the Solution Explorer and choose Generate Configurations to import the project's launch profiles into run/debug configurations.
If you remove all run/debug configurations from the solution and reopen it, JetBrains Rider will generate new run/debug configurations based on launch profiles in launchSettings.json.
Running and debugging launch profiles
When launch profiles are imported as run/debug configurations, you can choose the corresponding configuration on the toolbar and click Run or Debug :
If a project has launchSettings.json, but there are no corresponding run/debug configurations for some reason, you can right-click the project in the Solution Explorer and choose Run '...' or Debug '...'. In this case, JetBrains Rider will create a temporary run/debug configuration for the first launch profile in the project's launchSettings.json and execute it.
You can also open a launchSettings.json in the editor and use the gutter icons to run or debug any launch profile:
In this case, JetBrains Rider will also create a temporary run/debug configuration for this profile.
Editing launch settings profiles
A run/debug configurations based on a launch profile includes two kinds of parameters:
Parameters from launchSettings.json, which you can configure by editing the file — use syntax highlighting, code analysis, and code completion when editing:
Additional configuration parameters added by JetBrains Rider, such as the target framework to use or .NET runtime arguments. To configure these parameters, choosefrom the menu and pick the corresponding configuration.
Parameters from launchSettings.json are shown as read-only; all other parameters are editable:
Choose a startup project for this configuration.
A .NET Framework version that will be used to run this configuration.
Use this selector to pick one of the profiles configured in the launchSettings.json file.
The path to the executable file of the selected target project is calculated automatically, but you can change it if needed.
Arguments that will be passed to the executable when the configuration is started.
The working directory is automatically set to the bin/Debug path of the selected target project, but you can change it if needed.
Here you can specify custom environment variables for the target executable.
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 checkbox to show the output in an external window.
|The following four options are available when a IIS Express launch profile is chosen in the Launch profile: selector.|
To launch IIS Express with your ASP.NET Core application, JetBrains Rider uses a configuration file .idea/config/applicationhost.config, which is created using a template that ships with IIS Express. When possible, customizations you make to this file are also preserved. You might want to dispable this option for heavy customizations.
|Show IIS Express output|
This option enables output from the IIS Express process. By default, it is disabled (as the output is quite verbose), but when enabled we can see additional details when running the application:
|Send debug request|
When this option is enabled, JetBrains Rider will send an initial request (with a
|Additional IIS Express arguments|
This field lets you pass additional arguments to the IIS Express host (for example, to enable request tracing).
When you edit a run configuration (but not a run configuration template), you can specify the following options:
In this field, 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 through VCS
Select this checkbox to put the run/debug configuration under version control and make it available to other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder, while the local run/debug configurations are kept in the .idea\workspace.xml .
Allow running in parallel
If this checkbox is selected, it is possible to launch a run configuration multiple times in parallel instead of rerunning it. Each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
When disabled, every time a new instance of the 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. If you click OK in the confirmation dialog, the first instance of the runner will be stopped, and the next one will take its place. This makes sense when launching two instances of 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.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
View and edit the template (that is, the default settings) for the selected run/debug configuration. The templates are displayed under the Templates node and 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 the 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 or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
In this area you can specify tasks that must be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
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, if the checkbox is cleared, 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.