Correctly determine the 64-bit "Program Files" folder - fixes #1286 #1623
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.
The preferred way here would be just using
Environment.SpecialFolder.ProgramFiles
andEnvironment.SpecialFolder.ProgramFilesX86
for the two values, but that would require compilingFake.exe
asAnyCPU
(with "Prefer 32-bit" off).In a 32-bit process, both
Environment.SpecialFolder.ProgramFiles
and the environment variableProgramFiles
return the x86 folder. That means there is no official API to get the 64-bitProgram Files
folder from a 32-bit process, other than going to the registry, as mentioned in #1286.