Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

[release/3.1] Do not add x86 host to PATH on 64-bit machines#9212

Merged
NikolaMilosavljevic merged 1 commit into
dotnet:release/3.1from
NikolaMilosavljevic:host.x86.31
Jun 13, 2022
Merged

[release/3.1] Do not add x86 host to PATH on 64-bit machines#9212
NikolaMilosavljevic merged 1 commit into
dotnet:release/3.1from
NikolaMilosavljevic:host.x86.31

Conversation

@NikolaMilosavljevic
Copy link
Copy Markdown
Member

Backport of dotnet/runtime#69902 to dotnet/core-setup release/3.1

Fixes: dotnet/runtime#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: dotnet/runtime#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.

@NikolaMilosavljevic NikolaMilosavljevic changed the title Do not add x86 host to PATH on 64-bit machines [release/3.1] Do not add x86 host to PATH on 64-bit machines Jun 9, 2022
@carlossanlop
Copy link
Copy Markdown

Needs the servicing-consider label and a sign-off from area owners. Please also send an email to Tactics with a copy of the template so it is discussed for servicing.

@NikolaMilosavljevic
Copy link
Copy Markdown
Member Author

Needs the servicing-consider label and a sign-off from area owners. Please also send an email to Tactics with a copy of the template so it is discussed for servicing.

Thanks. Yeah, I know. I was waiting on some testing to be completed before adding reviewers, tags and sending to Tactics.

@NikolaMilosavljevic NikolaMilosavljevic added area-Setup Servicing-consider Issue for next servicing release review labels Jun 9, 2022
@NikolaMilosavljevic NikolaMilosavljevic added this to the 3.1 milestone Jun 9, 2022
@NikolaMilosavljevic
Copy link
Copy Markdown
Member Author

Approved offline - @joeloff @ericstj any concerns with this backport - can you approve it?

@NikolaMilosavljevic NikolaMilosavljevic added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jun 10, 2022
@NikolaMilosavljevic NikolaMilosavljevic merged commit 247255e into dotnet:release/3.1 Jun 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Setup Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants