Document which launch profile is used by default

[cremor]

Description

Please document which launch profile (from launchSettings.json) is used by default when you execute dotnet run without further arguments.

Previously, this article contained the sentence "As the first profile listed, this profile is used by default.", but this was removed in #36022 by @guardrex
(I found this because https://stackoverflow.com/a/74290687/631802 links here with this sentence as a quote.)

Page URL

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-10.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/environments.md

Document ID

1cb5eb30-dd84-e5e1-5826-d74243fabf04

Platform Id

3f914b6e-befc-c9a2-7712-d34a12a97fec

Article author

@tdykstra

Metadata

• ID: ceffa6a2-770c-1cd9-5145-dcd423f9dd22
• PlatformId: 3f914b6e-befc-c9a2-7712-d34a12a97fec
• Service: aspnet-core
• Sub-service: fundamentals

Related Issues

[guardrex]

Hello @cremor ... Yes, and it was retained in one of the Blazor articles as a NOTE ...

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.

It can appear both here and in the Blazor node's Environments article where launchSettings.json is discussed.

Tom, I'll take care of it. I have a minute here this morning. I'll ping you and Wade on the PR.