23

I would like to create a batch file to make the builds from my VS project in on click. All the days I do the following steps:

  1. Opens a cmd console as administrador
  2. Go to the path of my project/solution (using the CD.., CD commands)

  3. Write the following command to make the build:

    msbuild mySolution.sln /p:configuration=debug

As commented before, I'd like to make all this process in one simply click. So, I'm trying to create a .bat file to do it.

This is the code of my batch file:

set location="C:\myPath\..\MyFolderSolution"
set pathMSBuild = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe"

@echo off
cls

call %pathMSBuild%
cd %location%
msbuild.exe "lucre.sln" /p:configuration=debug
pause

However, when I try to execute the batch file I get the following error: 'msbuild' is not recognized as an internal or external command, operable program or batch file.

Any clue or help to know if it is possible and if so, how to do it will be very appreciate

Regards!

MikePR
  • 2,786
  • 5
  • 31
  • 64

4 Answers4

22

You're not in the right directory, you need to cd to the directory that msbuild is in. Try this:

set pathMSBuild="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\"
@echo off
cls
cd %pathMSBuild%
msbuild.exe "C:\myPath\..\MyFolderSolution\lucre.sln" /p:configuration=debug
pause

Or you could add the msbuild directory to your path, and skip the lines with set and cd.

stevejoy32
  • 354
  • 2
  • 5
  • Hi Steve. It works OK ;-) As you mentioned I was pointed out to a different location. Thanks so much – MikePR Jul 23 '13 at 22:13
  • 3
    probably better to use %WinDir% instead of `C:\Windows\` – knocte Mar 30 '17 at 08:26
  • Do not use whitespace between the name and value; `SET foo = bar` will not work but `SET foo=bar` will work (I can't edit the post because "Edits must be at least 6 characters"). – Xavier Peña Apr 25 '17 at 13:43
4

Both answers use hardcoded paths, which might not always work. Use this instead:

@if exist "%VS100COMNTOOLS%vsvars32.bat" call "%VS100COMNTOOLS%vsvars32.bat"

Change VS100 to any other version, you can also put these lines one by one to support many versions of VS simulteneously:

@if exist "%VS100COMNTOOLS%vsvars32.bat" call "%VS100COMNTOOLS%vsvars32.bat"
@if exist "%VS140COMNTOOLS%vsvars32.bat" call "%VS140COMNTOOLS%vsvars32.bat"

If done this way, you no longer dependant on a specific version of .Net Framework or Visual Studio

Archeg
  • 8,364
  • 7
  • 43
  • 90
  • Those are useful variables, thanks. In that same directory, the batch file `VsMSBuildCmd.bat` seems to be more specifically intended to create the environment for invoking `MSBuild.exe` – Reinier Torenbeek Feb 14 '18 at 15:24
4

You can also add the directory which MSBuild.exe is located, to the PATH environment variable so you can call msbuild anywhere.

So in the bat file it can be something like this:

cd C:\PathToSoultion\
msbuild TheSolutionName.sln /p:configuration=debug
pause

I know the question is already years away but I hope this might help someone.

johnsabre
  • 355
  • 2
  • 7
2

If you don't want to cd to the msbuild installation directory, you can also load the Visual Studio Environment Variables like this:

call "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" x86_amd64

(See also this Question)

Community
  • 1
  • 1
Vertigo
  • 634
  • 1
  • 9
  • 24