Clean some things up in the publishing article#55003
Open
adegeo wants to merge 2 commits into
Open
Conversation
adegeo
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
This PR refines the .NET application publishing overview article by adjusting section naming, adding guidance to avoid common CLI publishing pitfalls, and simplifying/removing some pivoted content.
Changes:
- Add an IMPORTANT note warning about mixing build and publish options when using
dotnet publish --no-build. - Rename several publishing mode section headings to the “Publish as …” format.
- Adjust the “Quick reference” section text and pivot structure.
Comments suppressed due to low confidence (4)
docs/core/deploying/index.md:249
- Renaming this heading changes its autogenerated anchor. Other docs deep-link into this page using
#self-contained-deployment, so those links will break unless you keep the old anchor ID.
## Publish as self-contained
docs/core/deploying/index.md:298
- Renaming this heading changes its autogenerated anchor. The Quick reference table links to
#single-file-deployment, so it will break unless you keep the old anchor ID (or update all references).
## Publish as single-file
docs/core/deploying/index.md:351
- Renaming this heading changes its autogenerated anchor. The Quick reference table links to
#native-aot-deployment, so it will break unless you keep the old anchor ID (or update all references).
## Publish as native AOT
docs/core/deploying/index.md:413
- Renaming this heading changes its autogenerated anchor. The Quick reference table (and any external deep links) still use
#readytorun-deployment, so those links will break unless you keep the old anchor ID.
## Publish as ReadyToRun
gewarren
reviewed
Jul 23, 2026
| | [Container deployment](#container-deployment) | `dotnet publish -c Release [-r <RID>] -t:PublishContainer` | | ||
|
|
||
| ::: zone-end | ||
| <a id="framework-dependent-deployment"></a> |
Collaborator
There was a problem hiding this comment.
Why are you adding bookmarks manually?
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.
Summary
Related to the issue, I had already performed quite a large face lift on this content, merging articles together and covering the 3 tools, VS, VSCode, CLI. I instead focused on some section naming, calling out a trap people might find themselves in, and removing the pivots related to the CLI cheat sheet.
Fixes #47080
Internal previews