64-bit MSBuild.exe is not used when custom process is 64-bit
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system
Research direction
Inspect the MSBuildLocator logic that selects MSBuild.exe for a custom process, using the reported AnyCPU configuration with Prefer32Bit disabled as the starting case. Reproduce the out-of-proc build failure and verify that a 64-bit process selects the 64-bit MSBuild.exe rather than the x86 installation.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- C#
- Stars
- 262
- Forks
- 91
- Avg merge
- 11d 22h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/MSBuildLocator
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
microsoft/MSBuildLocator#390 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 64/100
microsoft/MSBuildLocator#389 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/MSBuildLocator#380 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoft/MSBuildLocator#377 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/MSBuildLocator#371 · 1 comment ·
All issues in microsoft/MSBuildLocator
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·