dotnet · guardrex · May 29, 2026 · May 29, 2026 · May 29, 2026 · May 29, 2026
@@ -150,6 +150,8 @@ The `inspectUri` property:
 
 The placeholder values for the WebSocket protocol (`wsProtocol`), host (`url.hostname`), port (`url.port`), and inspector URI on the launched browser (`browserInspectUri`) are provided by the framework.
 
+[!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 ## Packages
 
 :::moniker range=">= aspnetcore-8.0"

@@ -112,6 +112,8 @@ For a standalone Blazor WebAssembly app running locally, the development server
 
 :::moniker-end
 
+[!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 For app's running locally in development, the app defaults to the `Development` environment. Publishing the app defaults the environment to `Production`.
 
 :::moniker range="< aspnetcore-5.0"
@@ -206,6 +208,8 @@ Although the Blazor framework issues the header name in kebab case with mixed le
 
 For local development runs with Blazor's built-in development server, you can control the value of the `Blazor-Environment` header by setting the value of the `ASPNETCORE_ENVIRONMENT` environment variable in the project's `Properties/launchSettings.json` file. When running locally with the development server, the order of precedence for determining the app's environment is [`Blazor.start` configuration (`environment` key)](#set-the-client-side-environment-via-blazor-startup-configuration) > `Blazor-Environment` response header (`blazor.boot.json` file) > `ASPNETCORE_ENVIRONMENT` environment variable (`launchSettings.json`). You can't use the `ASPNETCORE_ENVIRONMENT` environment variable (`launchSettings.json`) approach for a deployed Blazor WebAssembly app. The technique only works with the development server on local runs of the app.
 
+[!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 ### IIS
 
 In the following example for IIS, the custom header (`Blazor-Environment`) is added to the published `web.config` file. The `web.config` file is located in the `bin/Release/{TARGET FRAMEWORK}/publish` folder, where the `{TARGET FRAMEWORK}` placeholder is the target framework:

@@ -214,6 +214,8 @@ In many hosting scenarios, the relative URL path to the app is the root of the a
         "ASPNETCORE_ENVIRONMENT": "Development"
     }
     ```
+
+    [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
     
     For more information on the `launchSettings.json` file, see <xref:fundamentals/environments#development-and-launchsettingsjson>. For additional information on Blazor app base paths and hosting, see [`<base href="/" />` or base-tag alternative for Blazor MVC integration (dotnet/aspnetcore #43191)](https://github.com/dotnet/aspnetcore/issues/43191#issuecomment-1212156106).
 

@@ -397,6 +397,8 @@ The `--contentroot` argument sets the absolute path to the directory that contai
   "commandLineArgs": "--contentroot=/content-root-path"
   ```
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * In Visual Studio, specify the argument in **Properties** > **Debug** > **Application arguments**. Setting the argument in the Visual Studio property page adds the argument to the `launchSettings.json` file.
 
   ```console

@@ -79,8 +79,7 @@ An `_Imports.razor` file in each of the server and `.Client` projects includes c
 
 The `Properties` folder of the server project holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
-> [!NOTE]
-> The `http` profile precedes the `https` profile in the `launchSettings.json` file. When an app is run with the .NET CLI, the app runs at an HTTP endpoint because the first profile found is `http`. The profile order eases the transition of adopting HTTPS for Linux and macOS users. If you prefer to start the app with the .NET CLI without having to pass the `-lp https` or `--launch-profile https` option to the `dotnet watch` (or `dotnet run`) command, simply place the `https` profile above the `http` profile in the file.
+[!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
 
 The `wwwroot` folder of the server project is the [Web Root](xref:fundamentals/index#web-root) folder for the server project that holds the app's public static assets.
 
@@ -135,6 +134,8 @@ Project structure:
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components and stylesheets:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `MainLayout.razor.css`: Stylesheet for the app's main layout.
@@ -181,6 +182,8 @@ The Blazor Server template creates the initial files and directory structure for
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components and stylesheets:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `MainLayout.razor.css`: Stylesheet for the app's main layout.
@@ -226,6 +229,8 @@ The Blazor Server template creates the initial files and directory structure for
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components and stylesheets:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `MainLayout.razor.css`: Stylesheet for the app's main layout.
@@ -273,6 +278,8 @@ The Blazor Server template creates the initial files and directory structure for
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `NavMenu` component (`NavMenu.razor`): Implements sidebar navigation. Includes the [`NavLink` component](xref:blazor/fundamentals/navigation#navlink-component) (<xref:Microsoft.AspNetCore.Components.Routing.NavLink>), which renders navigation links to other Razor components. The <xref:Microsoft.AspNetCore.Components.Routing.NavLink> component automatically indicates a selected state when its component is loaded, which helps the user understand which component is currently displayed.
@@ -349,8 +356,7 @@ Project structure:
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
-  > [!NOTE]
-  > The `http` profile precedes the `https` profile in the `launchSettings.json` file. When an app is run with the .NET CLI, the app runs at an HTTP endpoint because the first profile found is `http`. The profile order eases the transition of adopting HTTPS for Linux and macOS users. If you prefer to start the app with the .NET CLI without having to pass the `-lp https` or `--launch-profile https` option to the `dotnet watch` (or `dotnet run`) command, simply place the `https` profile above the `http` profile in the file.
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
 
 * `wwwroot` folder: The [Web Root](xref:fundamentals/index#web-root) folder for the app containing the app's public static assets, including `appsettings.json` and environmental app settings files for [configuration settings](xref:blazor/fundamentals/configuration) and sample weather data (`sample-data/weather.json`). The `index.html` webpage is the root page of the app implemented as an HTML page:
   * When any page of the app is initially requested, this page is rendered and returned in the response.
@@ -387,6 +393,8 @@ Project structure:
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components and stylesheets:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `MainLayout.razor.css`: Stylesheet for the app's main layout.
@@ -443,6 +451,8 @@ The Blazor WebAssembly template creates the initial files and directory structur
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components and stylesheets:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `MainLayout.razor.css`: Stylesheet for the app's main layout.
@@ -495,6 +505,8 @@ The Blazor WebAssembly template creates the initial files and directory structur
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components and stylesheets:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `MainLayout.razor.css`: Stylesheet for the app's main layout.
@@ -547,6 +559,8 @@ The Blazor WebAssembly template creates the initial files and directory structur
 
 * `Properties` folder: Holds [development environment configuration](xref:fundamentals/environments#development-and-launchsettingsjson) in the `launchSettings.json` file.
 
+  [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 * `Shared` folder: Contains the following shared components:
   * `MainLayout` component (`MainLayout.razor`): The app's [layout component](xref:blazor/components/layouts).
   * `NavMenu` component (`NavMenu.razor`): Implements sidebar navigation. Includes the [`NavLink` component](xref:blazor/fundamentals/navigation#navlink-component) (<xref:Microsoft.AspNetCore.Components.Routing.NavLink>), which renders navigation links to other Razor components. The <xref:Microsoft.AspNetCore.Components.Routing.NavLink> component automatically indicates a selected state when its component is loaded, which helps the user understand which component is currently displayed.

@@ -426,7 +426,7 @@ dotnet watch
 
 The default browser is launched at `https://localhost:{PORT}`, which displays the app's UI. The `{PORT}` placeholder is the random port assigned at app creation. If you need to change the port due to a local port conflict, change the port in the project's `Properties/launchSettings.json` file.
 
-When an app created from the Blazor Web App project template is run with the .NET CLI, the app runs at an HTTP (insecure) endpoint because the first profile found in the app's launch settings file (`Properties/launchSettings.json`) is the HTTP (insecure) profile, which is named `http`. The HTTP profile was placed in the first position to ease the transition of adopting SSL/HTTPS security for non-Windows users.
+[!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
 
 One approach for running the app with SSL/HTTPS is to pass the [`-lp`|`--launch-profile` option](/dotnet/core/tools/dotnet-run#options) with the `https` profile name to the `dotnet watch` command:
 

@@ -163,6 +163,8 @@ The app is compiled and run. The app is launched at `http://localhost:{PORT}`, w
 
 Navigate the pages of the app to confirm that the app is working normally.
 
+[!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 :::zone-end
 
 ## Stop the app

diff --git a/aspnetcore/fundamentals/environments.md b/aspnetcore/fundamentals/environments.md
@@ -5,7 +5,7 @@ description: Learn how to set and control app behavior across runtime environmen
 monikerRange: '>= aspnetcore-3.1'
 ms.author: tdykstra
 ms.custom: mvc
-ms.date: 09/19/2025
+ms.date: 05/29/2026
 uid: fundamentals/environments
 ---
 # ASP.NET Core runtime environments
@@ -203,12 +203,14 @@ Profiles can be selected in the Visual Studio UI next to the Start button (►).
 
 When a solution contains multiple projects, only set the environment for the startup project.
 
-Alternatively, use the [`dotnet run`](/dotnet/core/tools/dotnet-run) command with the [`-lp|--launch-profile` option](/dotnet/core/tools/dotnet-run#options) set to the profile's name. *This approach only supports launch profiles based on the `Project` command.*
+Alternatively, use the [`dotnet watch`](/dotnet/core/tools/dotnet-watch) or [`dotnet run`](/dotnet/core/tools/dotnet-run) command with the [`-lp|--launch-profile` option](/dotnet/core/tools/dotnet-run#options) set to the profile's name. *This approach only supports launch profiles based on the `Project` command.*
 
 ```dotnetcli
 dotnet run -lp "https"
 ```
 
+[!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
+
 When using [Visual Studio Code](https://code.visualstudio.com/) with the [C# Dev Kit for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit) ([Getting Started with C# in VS Code](https://code.visualstudio.com/docs/csharp/get-started)), launch profiles are picked up from the app's `launchSettings.json` file.
 
 If the C# Dev Kit isn't used, set the `ASPNETCORE_ENVIRONMENT` environment variable in the `.vscode/launch.json` in the `env` section, along with any other environment variables set in the section:

diff --git a/aspnetcore/includes/default-launch-profile-for-dotnet-cli.md b/aspnetcore/includes/default-launch-profile-for-dotnet-cli.md
@@ -0,0 +1,2 @@
+> [!NOTE]
+> When an app is run with the .NET CLI, the first launch profile in `launchSettings.json` whose `commandName` is `Project` is used by default. To use a different profile (for example, `https`), pass the [`-lp|--launch-profile` option](/dotnet/core/tools/dotnet-run#options) to [`dotnet watch`](/dotnet/core/tools/dotnet-watch) or [`dotnet run`](/dotnet/core/tools/dotnet-run) or move the preferred profile to the top of the file.
-Original file line number
+Diff line change
@@ Expand Up @@
             "ASPNETCORE_ENVIRONMENT": "Development"
         }
         ```
+        [!INCLUDE[](~/includes/default-launch-profile-for-dotnet-cli.md)]
         For more information on the `launchSettings.json` file, see <xref:fundamentals/environments#development-and-launchsettingsjson>. For additional information on Blazor app base paths and hosting, see [`<base href="/" />` or base-tag alternative for Blazor MVC integration (dotnet/aspnetcore #43191)](https://github.com/dotnet/aspnetcore/issues/43191#issuecomment-1212156106).
@@ Expand Down @@
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		> [!NOTE]
		> When an app is run with the .NET CLI, the first launch profile in `launchSettings.json` whose `commandName` is `Project` is used by default. To use a different profile (for example, `https`), pass the [`-lp\|--launch-profile` option](/dotnet/core/tools/dotnet-run#options) to [`dotnet watch`](/dotnet/core/tools/dotnet-watch) or [`dotnet run`](/dotnet/core/tools/dotnet-run) or move the preferred profile to the top of the file.