Run and debug .NET Core and ASP.NET Core apps with launch profiles
A .NET Core or ASP.NET Core application can have its launch profiles configured with launchSettings.json. These profiles are auto-imported to the corresponding run/debug configurations, which you can then use to run and debug the application. Launch settings profiles for ASP.NET Core apps are often used to run and debug these apps in IIS Express.
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 Sample.
Create 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 run configurations were created in the solution before. If there are existing run/debug configurations or if you remove the auto-generated 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.
Run and debug 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, 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.
Edit launch settings profiles
A run/debug configuration 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, choose from the menu and pick the corresponding configuration.
Parameters from launchSettings.json are shown as read-only; the additional configuration parameters are editable:

Preferences of the '.NET Launch Settings Profile' run configuration
The available options depend on the commandName property of the selected launch profile in launchSettings.json. Profile parameters are read-only in this dialog. To change them, open the project's launchSettings.json file in the editor. If JetBrains Rider finds this file for the selected project, an open in the editor link appears next to the Profile parameters are set by... message. Click the link to open the file.
Project: | Choose a startup project for this configuration. |
Target framework: | A .NET Framework version that will be used to run this configuration. |
Launch profile: | Choose one of the profiles configured in the launchSettings.json file. |
Exe path: | Shows the executable path determined by the selected project and profile. For an |
Program arguments | Shows the arguments from the profile's |
Working directory: | Shows the profile's |
Environment variables: | Shows environment variables from the profile's |
Terminal mode: | This option is available when the selected launch profile has
|
Attach to child .NET processes | Automatically attach the debugger to child and grandchild .NET processes started by the application. Requires .NET 8 or later. Refer to Attach to child .NET processes. |
Runtime: | Choose a runtime for the application, or leave <Automatic> selected to let JetBrains Rider detect it. Available choices include .NET, Mono, and, on Windows, .NET Framework. Choose Add Custom Runtime… to select another .NET CLI executable. The Runtime selector is not available when the profile's |
Enable mixed-mode debugging | Debug managed .NET code and native C/C++ code in the same session. This option is available on Windows x64. Refer to Mixed-mode debugging. |
.NET runtime arguments: | Specify arguments for the runtime, separately from application arguments. This option is available when the profile's |
Application URL | Shows the profile's |
Launch URL | Shows the profile's |
After launch | Shows whether the profile opens a browser, as specified by |
with JavaScript debugger | Attach the JavaScript debugger when opening the browser. Requires a Chromium-based browser. Refer to Debug JavaScript in Chrome. |
Roslyn target project: | Shows the project used to debug a Roslyn component, such as a source generator. This field is read-only and appears only when the profile's |
The following options are available when an IIS Express launch profile is chosen in the Launch profile: selector. | |
IIS Express certificate | If the site requires an IIS Express developer certificate that is not installed, click Install Certificate to install it. |
Hosting model: | Shows the profile's |
Generate applicationhost.config | 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. Clear this checkbox to maintain the file manually. If the file exists, click open in the editor next to the checkbox to edit it. |
Show IIS Express output | Show output from the IIS Express process for additional diagnostics. This option is disabled by default: ![]() |
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). |
