Support using 64-bit MSBuild

MSBuild in Visual Studio ships with two MSBuild.exe entry points: the MSBuild\Current\bin folder has an x86 (32-bit) executable, and MSBuild\Current\bin\amd64 has a 64-bit (x64/amd64) executable.

In general, both can build any type of project, but some codebases benefit from the increased memory capacity of the 64-bit version.

The 32-bit MSBuild has been on PATH in the Developer Command Prompt in Visual Studio 2019 and prior, but Visual Studio 2022 puts 64-bit MSBuild on PATH to match Visual Studio which is now 64-bit.

This Action should expose an option to put 64-bit MSBuild on PATH instead of 32-bit. Azure DevOps has an option to do so in its MSBuild task:

msbuildArchitecture MSBuild Architecture

(Optional) Optionally supply the architecture (x86, x64) of MSBuild to run Default value: x86

For compatibility I would recommend keeping x86 the default; ideally that might change at some point in the future.

[rainersigwald]

I see no value in using x86 if x64 is available.

There can be some–if tasks are x86 but don’t tell MSBuild about it in the <UsingTask>, they can Just Work in x86-driven builds and fail in amd64-driven ones. And generally you don’t know that’s the case until you try a 64-bit build so it could be a surprising change here.

[timheuer]

Fixed with #65 merge and released in v1.1 tag – marketplace updated