Could not find MsBuild on your machine. Please set the MSBUILD variable to the location of MSBuild.exe and run razzle again. #12189

Closed
opened 2026-01-31 03:08:25 +00:00 by claunia · 6 comments
Owner

Originally created by @jonathanpepinmoore on GitHub (Jan 26, 2021).

Steps to reproduce

From A 2019 Dev Prompt Run: in the terminal root

.\tools\razzle.cmd

Expected behavior

environment variables set

Actual behavior

Untitled

The Powershell commands work it's razzle that does not and I don't know the format or -MSBuildPath.

Originally created by @jonathanpepinmoore on GitHub (Jan 26, 2021). # Steps to reproduce From A 2019 Dev Prompt Run: in the terminal root .\tools\razzle.cmd # Expected behavior environment variables set # Actual behavior ![Untitled](https://user-images.githubusercontent.com/8218836/105781328-41f6f900-5f27-11eb-8e0f-ea5b9b1d2b61.png) The Powershell commands work it's razzle that does not and I don't know the format or -MSBuildPath.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:08:25 +00:00
Author
Owner

@DHowett commented on GitHub (Jan 26, 2021):

Honestly, your best bet is going to be to just build it inside VS. We use vswhere to find msbuild, and if your VS install isn't showing up that will be an interesting discussion to have.

@DHowett commented on GitHub (Jan 26, 2021): Honestly, your best bet is going to be to just build it inside VS. We use vswhere to find msbuild, and if your VS install isn't showing up that will be an interesting discussion to have.
Author
Owner

@jonathanpepinmoore commented on GitHub (Jan 26, 2021):

I got it to build using 'nuget restore *.sln' and then msbuild. Razzle just does not work right now

Untitled2

I don't use Visual Studio 2019 just the build tools. I ran openbash.cmd, but OpenConsole.exe does not build in the solution yet. Only Microsoft.Terminal.Wpf.dll or I missed some build flags. nuget detects MSBUILD I might look of the razzle batch file. You might need the vs-setup-samples on github for the vswhere.cmd. I understand now the build configuration must be set Any CPU only builds the WPF dll.

@jonathanpepinmoore commented on GitHub (Jan 26, 2021): I got it to build using 'nuget restore *.sln' and then msbuild. Razzle just does not work right now ![Untitled2](https://user-images.githubusercontent.com/8218836/105782982-4b359500-5f2a-11eb-8148-812be69efd2b.png) I don't use Visual Studio 2019 just the build tools. I ran openbash.cmd, but OpenConsole.exe does not build in the solution yet. Only Microsoft.Terminal.Wpf.dll or I missed some build flags. nuget detects MSBUILD I might look of the razzle batch file. You might need the vs-setup-samples on github for the vswhere.cmd. I understand now the build configuration must be set Any CPU only builds the WPF dll.
Author
Owner

@jonathanpepinmoore commented on GitHub (Jan 26, 2021):

Untitled3

@jonathanpepinmoore commented on GitHub (Jan 26, 2021): ![Untitled3](https://user-images.githubusercontent.com/8218836/105786026-17aa3900-5f31-11eb-9275-0f4abb8e5bb0.png)
Author
Owner

@jonathanpepinmoore commented on GitHub (Jan 26, 2021):

set the build config to x64

@jonathanpepinmoore commented on GitHub (Jan 26, 2021): set the build config to x64
Author
Owner

@jonathanpepinmoore commented on GitHub (Jan 26, 2021):

\OpenConsole.sln /m /p:Configuration=Debug /p:Platform=x64 works there are 8 errors in the master branch.

@jonathanpepinmoore commented on GitHub (Jan 26, 2021): \OpenConsole.sln /m /p:Configuration=Debug /p:Platform=x64 works there are 8 errors in the master branch.
Author
Owner

@zadjii-msft commented on GitHub (Jan 26, 2021):

For the record, I don't run razzle from a VS dev prompt. I use that from a plain old cmd.exe.

@zadjii-msft commented on GitHub (Jan 26, 2021): For the record, I don't run `razzle` from a VS dev prompt. I use that from a plain old `cmd.exe`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12189