This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Fix initializing BuildTools when the Platform environment variable is set #24998
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.
Platform
variable before initializing BuildToolsbuild-test.cmd
exit ifinit-tools.cmd
failsSome BuildTools initialization steps fail if
Platform
is set to a value with which they are not compatible. We were relying ondotnet.cmd
to clear thePlatform
environment variable beforeinit-tools.cmd
was called.build-test.cmd
was always callinginit-tools.cmd
in such a way that thePlatform
variable was not cleared, but generally the tools would previously have been initialized throughdotnet.cmd
, so they would not be initialized again. With #24841, we stopped initializing BuildTools indotnet.cmd
, so the call inbuild-test.cmd
was actually doing the initialization (and failing depending on how `Platform is set).Fixes #24943