Add note about offline layout path behavior#11270
Add note about offline layout path behavior#11270MarkusAngenendt wants to merge 5 commits intoMicrosoftDocs:mainfrom
Conversation
|
Learn Build status updates of commit ae89952: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@microsoft-github-policy-service agree |
|
@MarkusAngenendt : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Pull request overview
This PR updates Visual Studio installation documentation to warn administrators that Visual Studio records the offline/local layout path and expects it to remain available at the same location for future updates or component additions.
Changes:
- Added an IMPORTANT callout explaining that the layout path is stored in
state.jsonand should not be moved. - Added a cross-reference note in the “deploy a layout onto a client machine” article pointing readers to the detailed explanation.
- Removed a couple of stray blank lines in the offline installation article.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/install/deploy-a-layout-onto-a-client-machine.md | Adds an IMPORTANT callout reminding readers to keep the layout location stable and links to the detailed guidance. |
| docs/install/create-an-offline-installation-of-visual-studio.md | Adds an IMPORTANT callout documenting where the installer records the layout path and why moving the layout can break updates/components. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
docs/install/create-an-offline-installation-of-visual-studio.md
Outdated
Show resolved
Hide resolved
docs/install/create-an-offline-installation-of-visual-studio.md
Outdated
Show resolved
Hide resolved
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Correct Copilot suggestions
Correct Copilot suggestions
Correct Copilot suggestions
|
Learn Build status updates of commit 86f7d03: ✅ Validation status: passed
For more details, please refer to the build report. |
Correct Copilot suggestions
|
Learn Build status updates of commit bccd7fb: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit f7473d8: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Those were good suggestions! I’ve applied and committed them. |
|
@anandmeg Could you review this proposed update to your article and enter Thanks! |
This PR adds a note explaining that the Visual Studio installer recordes the offline layout path in the state.json, and that future updates or component additions require the layout to remain available at the same path.
I encountered repeated installation failures when trying to add a workload to an existing Visual Studio instance because the layout had been moved to a different location. The behavior is currently not documented and can lead to time-consuming troubleshooting and log reading for administrators.