Add note on the .NET CLI default launch profile#37205
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR documents which launchSettings.json launch profile the .NET CLI uses by default (when dotnet run/dotnet watch is executed without specifying a launch profile), and reuses the guidance across multiple ASP.NET Core and Blazor articles via a shared include.
Changes:
- Adds a reusable include explaining the default .NET CLI launch profile behavior and how to select a different profile.
- Updates the main ASP.NET Core Environments article to reference the new include and refreshes
ms.date. - Replaces/augments existing Blazor guidance with the shared include across several articles.
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| aspnetcore/includes/default-launch-profile-for-dotnet-cli.md | New reusable include explaining default .NET CLI launch profile selection. |
| aspnetcore/fundamentals/environments.md | Updates CLI guidance and ms.date; includes the new launch profile note. |
| aspnetcore/blazor/tutorials/movie-database-app/part-1.md | Adds the shared include after CLI run instructions. |
| aspnetcore/blazor/tooling.md | Replaces inline text with the shared include in the CLI pivot. |
| aspnetcore/blazor/project-structure.md | Replaces repeated NOTE blocks with the shared include in multiple template structure sections. |
| aspnetcore/blazor/host-and-deploy/webassembly/index.md | Adds the shared include near launchSettings.json guidance. |
| aspnetcore/blazor/host-and-deploy/app-base-path.md | Adds the shared include in the launchSettings.json section. |
| aspnetcore/blazor/fundamentals/environments.md | Adds the shared include in two places related to environment configuration. |
| aspnetcore/blazor/debug.md | Adds the shared include near local debugging guidance. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
wadepickett
approved these changes
May 29, 2026
Contributor
wadepickett
left a comment
There was a problem hiding this comment.
Well done! I can't find any issues. Great work. Approved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #37204
Thanks @cremor! 🚀
Tom, Wade ... Just need one review to get this in.
I place a NOTE in an INCLUDES file for this one because I'd like to use it in several Blazor node articles. For the main doc set's Environments article, I update the
ms.date.If you feel that we should place this as normal text, I'll strip the NOTE designation, leaving this content as a paragraph in the INCLUDES file. It could go either way. NOTEs do break up the flow of the text. I'm on the fence about it. 😄
BTW ... I disagreed with Copilot's recommendation on the structure of the last sentence of the INCLUDES file. It prefers two assumed "you" imperative tense subjects ("[you] pass ... , or [you] move ..."), but I prefer one subject. So, I went with the sentence structure "[you] pass ... or move ..." without a comma.
Internal previews