Skip to content

Refactor vsRequirements assignment logic in tools.ps1#16313

Closed
marcpopMSFT wants to merge 1 commit intorelease/9.0from
marcpopMSFT-patch-1
Closed

Refactor vsRequirements assignment logic in tools.ps1#16313
marcpopMSFT wants to merge 1 commit intorelease/9.0from
marcpopMSFT-patch-1

Conversation

@marcpopMSFT
Copy link
Member

Because 17.14 went stable, we needed a way to run vswhere, find the VS node, and enable preview SDKs. Noah found a way to do this but he had to modify tools.ps1 because the SDK repo didn't have a VS node in our global.json

https://github.com/dotnet/sdk/pull/51558/files#diff-72b8f8e899b94872c6ead31fd06ec109da15bcb9ad2af6e78103d6763a31c637

Porting his change here to see if folks want this centrally. Alternatively, I'm trying adding the vs node to global.json to see if it unblocks us.

To double check:

Because 17.14 went stable, we needed a way to run vswhere, find the VS node, and enable preview SDKs. Noah found a way to do this but he had to modify tools.ps1 because the SDK repo didn't have a VS node in our global.json

https://github.com/dotnet/sdk/pull/51558/files#diff-72b8f8e899b94872c6ead31fd06ec109da15bcb9ad2af6e78103d6763a31c637

Porting his change here to see if folks want this centrally. Alternatively, I'm trying adding the vs node to global.json to see if it unblocks us.
Copilot AI added a commit that referenced this pull request Nov 14, 2025
Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com>
@marcpopMSFT
Copy link
Member Author

chcosta is going to try to bake prerelease support configuration for VS into the images so hopefully we don't need this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant