Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET MU docs #43429

Open
wants to merge 21 commits into
base: main
Choose a base branch
from
Open

.NET MU docs #43429

wants to merge 21 commits into from

Conversation

joeloff
Copy link
Member

@joeloff joeloff commented Nov 12, 2024

Summary

Add documentation that describe configuring Microsoft Update for .NET. This pulls together some content from various blog posts and includes additional options introduced during .NET 9 to better support .NET updates for FDD applications.


Internal previews

📄 File 🔗 Preview link
docs/core/install/windows.md Install .NET on Windows

@joeloff
Copy link
Member Author

joeloff commented Nov 12, 2024

[update] Think I figured this out

What is the relative link to use for absolute URLs outside of .NET docs?

'https://learn.microsoft.com/windows/win32/setupapi/run-and-runonce-registry-keys' will be broken in isolated environments. Replace with a relative link.

@jamshedd
Copy link
Member

@joeloff the content is fine, but I have a concern with the placement of the text within the MU section. I'm assuming the new ability to defer reboots is not limited to FDD installs deployed via MU, it can be used even if a customer is deploying the installer themselves in some other way? If so can we place this outside of the MU specific section?

@joeloff
Copy link
Member Author

joeloff commented Nov 12, 2024

@joeloff the content is fine, but I have a concern with the placement of the text within the MU section. I'm assuming the new ability to defer reboots is not limited to FDD installs deployed via MU, it can be used even if a customer is deploying the installer themselves in some other way? If so can we place this outside of the MU specific section?

I see your point. The feature was introduced to specifically deal with the MU situation, but you'd see it if the update is quietly installed and run under SYSTEM, e.g. if you manually pushed it out using SCCM.

I can move it to the troubleshoot section in the main windows.md doc, would that work better?

@joeloff
Copy link
Member Author

joeloff commented Nov 12, 2024

@jamshedd I updated the docs based on what we discussed

I kept MU in a separate MD file, but it's included under the Install .NET section in the Windows.md file. I moved the deferral section out as a separate, more general "choose when to remove" and included a note about availability and impact because things like WinGet uses the standalone installers too

Co-authored-by: Jamshed Damkewala <[email protected]>
Copy link
Contributor

@gewarren gewarren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding this. Tagging @adegeo too.

docs/core/install/windows.md Outdated Show resolved Hide resolved
docs/core/install/windows.md Outdated Show resolved Hide resolved
docs/core/install/windows.md Outdated Show resolved Hide resolved
docs/core/install/windows.md Outdated Show resolved Hide resolved
docs/core/install/windows.md Outdated Show resolved Hide resolved
docs/core/install/includes/microsoft-update.md Outdated Show resolved Hide resolved
docs/core/install/includes/microsoft-update.md Outdated Show resolved Hide resolved
docs/core/install/includes/microsoft-update.md Outdated Show resolved Hide resolved
docs/core/install/includes/microsoft-update.md Outdated Show resolved Hide resolved
docs/core/install/includes/microsoft-update.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants