Update winget install instructions in windows-requirements.md

[EgorBo]

Small refresh of the winget section in docs/workflow/requirements/windows-requirements.md.

Tested on a real clean win-arm64 machine.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
15 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

Updates the Windows developer setup documentation to refresh the winget-based installation instructions, especially around Visual Studio installation, to better align with the repo’s .vsconfig.

Changes:

• Update winget Python install from Python.Python.3.11 to Python.Python.3.14.
• Update Visual Studio winget install command to use Microsoft.VisualStudio.Community and pass the repo’s .vsconfig.
• Add a short explanatory note about using .vsconfig and Arm64 winget behavior for Visual Studio.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

docs/workflow/requirements/windows-requirements.md:97

• The --config path in the Visual Studio --override string isn’t quoted. If the runtime repo path contains spaces, the VS bootstrapper may split the path into multiple args and fail to find .vsconfig. Quote the expanded path within the override value.

winget install -e --id Microsoft.VisualStudio.Community --override "--passive --wait --config $PWD\.vsconfig"

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

docs/workflow/requirements/windows-requirements.md:97

• The --config $PWD\.vsconfig argument is unquoted inside the --override string, which will break if the repo path contains spaces (the VS bootstrapper will see a split argument). Also, using $PWD\.vsconfig implicitly assumes the command is run from the repo root (and that .vsconfig is already available), which isn’t stated here.

Consider using an explicit <path-to-runtime-repo>\.vsconfig placeholder and quoting the path within the override string (PowerShell needs doubled quotes inside a double-quoted argument).

winget install -e --id Microsoft.VisualStudio.Community --override "--passive --wait --config $PWD\.vsconfig"

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

docs/workflow/requirements/windows-requirements.md:97

• The Visual Studio --config path is not quoted. If the repo path contains spaces (common on Windows), the installer will treat it as multiple arguments and the command can fail. Quote the config path inside the --override string.

winget install -e --id Microsoft.VisualStudio.Community --override "--passive --wait --config $PWD\.vsconfig"

docs/workflow/requirements/windows-requirements.md:101

• The PR description says an Arm64 note was added (including the -a x64 workaround if winget refuses to fall back), but the updated winget section in this file doesn't include it. Either add the note here or adjust the PR description to match.

The last command installs the components listed in the repo's [`.vsconfig`](https://github.com/dotnet/runtime/blob/main/.vsconfig), so run it from the root of your clone.

[EgorBo]

PTAL @jkoritzinsky