Add securityContext to configuration file #5309
Merged
Conversation
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
Trenly
approved these changes
Mar 19, 2025
|
I thought the Visual Studio install didn't need elevation, but I haven't installed it "fresh" on a box in a while. |
denelon
approved these changes
Mar 19, 2025
It does on a completely fresh install, one where the "Visual studio Installer" isn't present yet. See the GIF -
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Setting developer mode, installing Visual Studio 2022 & fetching and installing VS components all require elevation. Added
securityContext: elevatedfor these resources. RemovedallowPrerelease: trueforMicrosoft.WinGet.DSC/WinGetPackageas it's GA now. Also fixed a bad link in the docsMicrosoft Reviewers: Open in CodeFlow