Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

64-bit MSBuild.exe is not used when custom process is 64-bit #133

Open
jeffkl opened this issue Aug 23, 2021 · 0 comments
Open

64-bit MSBuild.exe is not used when custom process is 64-bit #133

jeffkl opened this issue Aug 23, 2021 · 0 comments

Comments

@jeffkl
Copy link

jeffkl commented Aug 23, 2021

If you create a custom application that is AnyCPU but prefer 32-bit is set to false, then MSBuild locator will register the 32-bit MSBuild. This breaks out-of-proc builds with an error like this:

Build was canceled. Failed to successfully launch or connect to a child MSBuild.exe process. 
Verify that the MSBuild.exe "C:\Program Files (x86)\Visual Studio 2019 Preview\MSBuild\Current\Bin\MSBuild.exe"
 launches successfully, and that it is loading the same microsoft.build.dll that the launching process loaded.
 If the location seems incorrect, try specifying the correct location in the BuildParameters object, or with
 the MSBUILD_EXE_PATH environment variable.

This is because the handshake between the 64-bit application and the 32-bit MSBuild.exe doesn't match up. MSBuildLocator should use the 64-bit MSBuild.exe if Environment.Is64BitProcess is true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant