[release/6.0] Do not add x86 host to PATH on 64-bit machines #70299
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.
Backport of #69902 to release/6.0
Fixes: #70039
Customer Impact
This fixes the remaining issue with non-native host paths in machine's environment (PATH).
The fix uses a different model than x64-on-arm64. It is a simpler change as it's easy to determine if machine is 64-bit, using WersionNT64 property. This solution avoids unnecessary changes in arcade infra and adding additional complexity.
Testing
See main issue: #70039 (comment)
Risk
As with any breaking change, this will affect some users. In this case, anyone that wants 32-bit host (dotnet.exe) to be in PATH on 64-bit machines, will need to add host location to PATH manually.