blocks|key|1679087|text|查看注册表，看起来像是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1679088|HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0|code-block|syntax|javascript|1679089|这可能就是你想要的；打开regedit.exe看看吧。|1679090|通过命令行查询(每个Nikolay+Botev)|offset|length|1679091|reg.exe+query+"HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0"+/v+MSBuildToolsPath|1679092|通过PowerShell查询(每个MovGP0)|1679093|dir+HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\|1679094|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/15446618/712526|1|https://stackoverflow.com/a/31404176/712526^0|0|0|0|A|D|0|0|0|H|6|1|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|15|8|@]|9|@$K|16|L|17|1|18]]|A|$]]|$1|M|3|N|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1A|8|@]|9|@$K|1B|L|1C|1|1D]]|A|$]]|$1|Q|3|R|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

Poking around the registry, it looks like

<pre><code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0
</code></pre>

may be what you're after; fire up regedit.exe and have a look.

<h3>Query via command line (per <a href="https://stackoverflow.com/a/15446618/712526">Nikolay Botev</a>)</h3>

<pre><code>reg.exe query "HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0" /v MSBuildToolsPath
</code></pre>

<h3>Query via PowerShell (per <a href="https://stackoverflow.com/a/31404176/712526">MovGP0</a>)</h3>

<pre><code>dir HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\
</code></pre>

blocks|key|1464097|text|您还可以将MSBuild.exe的路径打印到命令行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1464098|reg.exe+query+"HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0"+/v+MSBuildToolsPath|code-block|syntax|javascript|1464099|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can also print the path of MSBuild.exe to the command line:

<pre><code>reg.exe query "HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0" /v MSBuildToolsPath
</code></pre>

blocks|key|1463966|text|如果您想对.Net+4使用MSBuild，那么您可以使用以下PowerShell命令来获取可执行文件的路径。如果你想要2.0或3.5版本，那么只需修改$dotNetVersion变量即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1463967|要运行可执行文件，您需要在$msbuild变量前面加上&。将执行该变量的。|1463968|#+valid+versions+are+[2.0,+3.5,+4.0]
$dotNetVersion+=+"4.0"
$regKey+=+"HKLM:\software\Microsoft\MSBuild\ToolsVersions\$dotNetVersion"
$regProperty+=+"MSBuildToolsPath"

$msbuildExe+=+join-path+-path+(Get-ItemProperty+$regKey).$regProperty+-childpath+"msbuild.exe"

&$msbuildExe|code-block|syntax|javascript|1463969|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you want to use MSBuild for .Net 4 then you can use the following PowerShell command to get the executable's path. If you want version 2.0 or 3.5 then just change the $dotNetVersion variable.

To run the executable you'll need to prepend the $msbuild variable with &amp;. That will execute the variable. 

<pre><code># valid versions are [2.0, 3.5, 4.0]
$dotNetVersion = "4.0"
$regKey = "HKLM:\software\Microsoft\MSBuild\ToolsVersions\$dotNetVersion"
$regProperty = "MSBuildToolsPath"

$msbuildExe = join-path -path (Get-ItemProperty $regKey).$regProperty -childpath "msbuild.exe"

&amp;$msbuildExe
</code></pre>

blocks|key|1464037|text|对于Windows7中的cmd+shell脚本，我在批处理文件中使用以下片段来查找.NET框架版本4中的MSBuild.exe。我假设版本4存在，但不要假设子版本。这不是完全通用的，但对于快速脚本，它可能会有所帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1464038|set+msbuild.exe=
for+/D+%25%25D+in+(%25SYSTEMROOT%25\Microsoft.NET\Framework\v4*)+do+set+msbuild.exe=%25%25D\MSBuild.exe|code-block|syntax|javascript|1464039|对于我的用途，如果不起作用，我将退出批处理文件，并返回错误：|1464040|if+not+defined+msbuild.exe+echo+error:+can't+find+MSBuild.exe+&+goto+:eof
if+not+exist+"%25msbuild.exe%25"+echo+error:+%25msbuild.exe%25:+not+found+&+goto+:eof|1464041|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For cmd shell scripting in Windows 7, I use the following fragment in my batch file to find MSBuild.exe in the .NET Framework version 4. I assume version 4 is present, but don't assume the sub-version. This isn't totally general-purpose, but for quick scripts it may be helpful:

<pre><code>set msbuild.exe=
for /D %%D in (%SYSTEMROOT%\Microsoft.NET\Framework\v4*) do set msbuild.exe=%%D\MSBuild.exe
</code></pre>

For my uses I'm exiting the batch file with an error if that didn't work:

<pre><code>if not defined msbuild.exe echo error: can't find MSBuild.exe &amp; goto :eof
if not exist "%msbuild.exe%" echo error: %msbuild.exe%: not found &amp; goto :eof
</code></pre>

blocks|key|1464306|text|您可以使用这个非常试用的PowerShell命令从注册表中获取MSBuildToolsPath。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1464307|PowerShell+(来自注册表)|1464308|Resolve-Path+HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\*+%7C+
Get-ItemProperty+-Name+MSBuildToolsPath|code-block|syntax|javascript|1464309|输出|1464310|MSBuildToolsPath+:+C:\Program+Files+(x86)\MSBuild\12.0\bin\amd64\
PSPath+++++++++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\12.0
PSParentPath+++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName++++++:+12.0
PSDrive++++++++++:+HKLM
PSProvider+++++++:+Microsoft.PowerShell.Core\Registry

MSBuildToolsPath+:+C:\Program+Files+(x86)\MSBuild\14.0\bin\amd64\
PSPath+++++++++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0
PSParentPath+++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName++++++:+14.0
PSDrive++++++++++:+HKLM
PSProvider+++++++:+Microsoft.PowerShell.Core\Registry

MSBuildToolsPath+:+C:\Windows\Microsoft.NET\Framework64\v2.0.50727\
PSPath+++++++++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0
PSParentPath+++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName++++++:+2.0
PSDrive++++++++++:+HKLM
PSProvider+++++++:+Microsoft.PowerShell.Core\Registry

MSBuildToolsPath+:+C:\Windows\Microsoft.NET\Framework64\v3.5\
PSPath+++++++++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5
PSParentPath+++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName++++++:+3.5
PSDrive++++++++++:+HKLM
PSProvider+++++++:+Microsoft.PowerShell.Core\Registry

MSBuildToolsPath+:+C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
PSPath+++++++++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0
PSParentPath+++++:+Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName++++++:+4.0
PSDrive++++++++++:+HKLM
PSProvider+++++++:+Microsoft.PowerShell.Core\Registry|1464311|或从文件系统|1464312|PowerShell+(来自文件系统)|1464313|Resolve-Path+"C:\Program+Files+(x86)\MSBuild\*\Bin\amd64\MSBuild.exe"
Resolve-Path+"C:\Program+Files+(x86)\MSBuild\*\Bin\MSBuild.exe"|1464314|1464315|Path
----
C:\Program+Files+(x86)\MSBuild\12.0\Bin\amd64\MSBuild.exe
C:\Program+Files+(x86)\MSBuild\14.0\Bin\amd64\MSBuild.exe
C:\Program+Files+(x86)\MSBuild\12.0\Bin\MSBuild.exe
C:\Program+Files+(x86)\MSBuild\14.0\Bin\MSBuild.exe|1464316|entityMap^0|V|G|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|15|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|16|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|17|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|18|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|19|8|@]|D|@]|E|$]]|$1|U|3|V|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|W|3|N|5|6|7|1B|8|@]|D|@]|E|$]]|$1|X|3|Y|5|J|7|1C|8|@]|D|@]|E|$K|L]]|$1|Z|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|10|$]]

You can use this very trial PowerShell Command to get the <code>MSBuildToolsPath</code> from the registry.

<h1>PowerShell (from registry)</h1>

<pre><code>Resolve-Path HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\* | 
Get-ItemProperty -Name MSBuildToolsPath
</code></pre>

<h2>Output</h2>

<pre><code>MSBuildToolsPath : C:\Program Files (x86)\MSBuild\12.0\bin\amd64\
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\12.0
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName : 12.0
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

MSBuildToolsPath : C:\Program Files (x86)\MSBuild\14.0\bin\amd64\
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName : 14.0
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

MSBuildToolsPath : C:\Windows\Microsoft.NET\Framework64\v2.0.50727\
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName : 2.0
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

MSBuildToolsPath : C:\Windows\Microsoft.NET\Framework64\v3.5\
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName : 3.5
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

MSBuildToolsPath : C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions
PSChildName : 4.0
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry
</code></pre>

or from the filesystem

<h1>PowerShell (from file system)</h1>

<pre><code>Resolve-Path "C:\Program Files (x86)\MSBuild\*\Bin\amd64\MSBuild.exe"
Resolve-Path "C:\Program Files (x86)\MSBuild\*\Bin\MSBuild.exe"
</code></pre>

<h2>Output</h2>

<pre><code>Path
----
C:\Program Files (x86)\MSBuild\12.0\Bin\amd64\MSBuild.exe
C:\Program Files (x86)\MSBuild\14.0\Bin\amd64\MSBuild.exe
C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe
C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe
</code></pre>

blocks|key|1464177|text|@AllenSanborn有一个很棒的powershell版本，但有些人要求只使用批处理脚本进行构建。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1464178|这是@bono8106回答的应用版本。|1464179|msbuildpath.bat|1464180|@echo+off

reg.exe+query+"HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0"+/v+MSBuildToolsPath+>+nul+2>&1
if+ERRORLEVEL+1+goto+MissingMSBuildRegistry

for+/f+"skip=2+tokens=2,*"+%25%25A+in+('reg.exe+query+"HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0"+/v+MSBuildToolsPath')+do+SET+"MSBUILDDIR=%25%25B"

IF+NOT+EXIST+"%25MSBUILDDIR%25"+goto+MissingMSBuildToolsPath
IF+NOT+EXIST+"%25MSBUILDDIR%25msbuild.exe"+goto+MissingMSBuildExe

exit+/b+0

goto:eof
::ERRORS
::---------------------
:MissingMSBuildRegistry
echo+Cannot+obtain+path+to+MSBuild+tools+from+registry
goto:eof
:MissingMSBuildToolsPath
echo+The+MSBuild+tools+path+from+the+registry+'%25MSBUILDDIR%25'+does+not+exist
goto:eof
:MissingMSBuildExe
echo+The+MSBuild+executable+could+not+be+found+at+'%25MSBUILDDIR%25'
goto:eof|code-block|syntax|javascript|1464181|build.bat|1464182|@echo+off
call+msbuildpath.bat
"%25MSBUILDDIR%25msbuild.exe"+foo.csproj+/p:Configuration=Release|1464183|对于Visual+Studio2017/+MSBuild+15，Aziz+Atif+(编写Elmah的人)编写了一个批处理脚本|offset|length|1464184|build.cmd+Release+Foo.csproj|1464185|https://github.com/linqpadless/LinqPadless/blob/master/build.cmd|1464186|@echo+off
setlocal
if+"%25PROCESSOR_ARCHITECTURE%25"=="x86"+set+PROGRAMS=%25ProgramFiles%25
if+defined+ProgramFiles(x86)+set+PROGRAMS=%25ProgramFiles(x86)%25
for+%25%25e+in+(Community+Professional+Enterprise)+do+(
++++if+exist+"%25PROGRAMS%25\Microsoft+Visual+Studio\2017\%25%25e\MSBuild\15.0\Bin\MSBuild.exe"+(
++++++++set+"MSBUILD=%25PROGRAMS%25\Microsoft+Visual+Studio\2017\%25%25e\MSBuild\15.0\Bin\MSBuild.exe"
++++)
)
if+exist+"%25MSBUILD%25"+goto+:restore
set+MSBUILD=
for+%25%25i+in+(MSBuild.exe)+do+set+MSBUILD=%25%25~dpnx$PATH:i
if+not+defined+MSBUILD+goto+:nomsbuild
set+MSBUILD_VERSION_MAJOR=
set+MSBUILD_VERSION_MINOR=
for+/f+"delims=.+tokens=1,2,3,4"+%25%25m+in+('msbuild+/version+/nologo')+do+(
++++set+MSBUILD_VERSION_MAJOR=%25%25m
++++set+MSBUILD_VERSION_MINOR=%25%25n
)
if+not+defined+MSBUILD_VERSION_MAJOR+goto+:nomsbuild
if+not+defined+MSBUILD_VERSION_MINOR+goto+:nomsbuild
if+%25MSBUILD_VERSION_MAJOR%25+lss+15++++goto+:nomsbuild
if+%25MSBUILD_VERSION_MINOR%25+lss+1+++++goto+:nomsbuild
:restore
for+%25%25i+in+(NuGet.exe)+do+set+nuget=%25%25~dpnx$PATH:i
if+"%25nuget%25"==""+(
++++echo+WARNING!+NuGet+executable+not+found+in+PATH+so+build+may+fail!
++++echo+For+more+on+NuGet,+see+https://github.com/nuget/home
)
pushd+"%25~dp0"
nuget+restore+%5E
+&&+call+:build+Debug+++%25*+%5E
+&&+call+:build+Release+%25*
popd
goto+:EOF

:build
setlocal
"%25MSBUILD%25"+/p:Configuration=%251+/v:m+%252+%253+%254+%255+%256+%257+%258+%259
goto+:EOF

:nomsbuild
echo+Microsoft+Build+version+15.1+(or+later)+does+not+appear+to+be
echo+installed+on+this+machine,+which+is+required+to+build+the+solution.
exit+/b+1|1464187|entityMap|0|LINK|mutability|MUTABLE|url|https://elmah.github.io/|1^0|0|0|0|0|0|0|19|5|0|0|0|0|1S|1|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1A|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|1C|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|1D|8|@]|9|@$Q|1E|R|1F|1|1G]]|A|$]]|$1|S|3|T|5|H|7|1H|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1I|8|@]|9|@$Q|1J|R|1K|1|1L]]|A|$]]|$1|W|3|X|5|H|7|1M|8|@]|9|@]|A|$I|J]]|$1|Y|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|V]]]]

@AllenSanborn has a great powershell version, but some folks have a requirement to use only batch scripts for builds.

This is an applied version of what @bono8106 answered.

msbuildpath.bat

<pre><code>@echo off

reg.exe query "HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0" /v MSBuildToolsPath &gt; nul 2&gt;&amp;1
if ERRORLEVEL 1 goto MissingMSBuildRegistry

for /f "skip=2 tokens=2,*" %%A in ('reg.exe query "HKLM\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0" /v MSBuildToolsPath') do SET "MSBUILDDIR=%%B"

IF NOT EXIST "%MSBUILDDIR%" goto MissingMSBuildToolsPath
IF NOT EXIST "%MSBUILDDIR%msbuild.exe" goto MissingMSBuildExe

exit /b 0

goto:eof
::ERRORS
::---------------------
:MissingMSBuildRegistry
echo Cannot obtain path to MSBuild tools from registry
goto:eof
:MissingMSBuildToolsPath
echo The MSBuild tools path from the registry '%MSBUILDDIR%' does not exist
goto:eof
:MissingMSBuildExe
echo The MSBuild executable could not be found at '%MSBUILDDIR%'
goto:eof
</code></pre>

build.bat

<pre><code>@echo off
call msbuildpath.bat
"%MSBUILDDIR%msbuild.exe" foo.csproj /p:Configuration=Release
</code></pre>

For Visual Studio 2017 / MSBuild 15, Aziz Atif (the guy who wrote <a href="https://elmah.github.io/" rel="nofollow noreferrer">Elmah</a>) wrote a batch script

<pre><code>build.cmd Release Foo.csproj
</code></pre>

<a href="https://github.com/linqpadless/LinqPadless/blob/master/build.cmd" rel="nofollow noreferrer">https://github.com/linqpadless/LinqPadless/blob/master/build.cmd</a>

<pre><code>@echo off
setlocal
if "%PROCESSOR_ARCHITECTURE%"=="x86" set PROGRAMS=%ProgramFiles%
if defined ProgramFiles(x86) set PROGRAMS=%ProgramFiles(x86)%
for %%e in (Community Professional Enterprise) do (
 if exist "%PROGRAMS%\Microsoft Visual Studio\2017\%%e\MSBuild\15.0\Bin\MSBuild.exe" (
 set "MSBUILD=%PROGRAMS%\Microsoft Visual Studio\2017\%%e\MSBuild\15.0\Bin\MSBuild.exe"
 )
)
if exist "%MSBUILD%" goto :restore
set MSBUILD=
for %%i in (MSBuild.exe) do set MSBUILD=%%~dpnx$PATH:i
if not defined MSBUILD goto :nomsbuild
set MSBUILD_VERSION_MAJOR=
set MSBUILD_VERSION_MINOR=
for /f "delims=. tokens=1,2,3,4" %%m in ('msbuild /version /nologo') do (
 set MSBUILD_VERSION_MAJOR=%%m
 set MSBUILD_VERSION_MINOR=%%n
)
if not defined MSBUILD_VERSION_MAJOR goto :nomsbuild
if not defined MSBUILD_VERSION_MINOR goto :nomsbuild
if %MSBUILD_VERSION_MAJOR% lss 15 goto :nomsbuild
if %MSBUILD_VERSION_MINOR% lss 1 goto :nomsbuild
:restore
for %%i in (NuGet.exe) do set nuget=%%~dpnx$PATH:i
if "%nuget%"=="" (
 echo WARNING! NuGet executable not found in PATH so build may fail!
 echo For more on NuGet, see https://github.com/nuget/home
)
pushd "%~dp0"
nuget restore ^
 &amp;&amp; call :build Debug %* ^
 &amp;&amp; call :build Release %*
popd
goto :EOF

:build
setlocal
"%MSBUILD%" /p:Configuration=%1 /v:m %2 %3 %4 %5 %6 %7 %8 %9
goto :EOF

:nomsbuild
echo Microsoft Build version 15.1 (or later) does not appear to be
echo installed on this machine, which is required to build the solution.
exit /b 1
</code></pre>

blocks|key|1679640|text|这适用于Visual+Studio+2015和2017：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1679641|function+Get-MSBuild-Path+{

++++$vs14key+=+"HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0"
++++$vs15key+=+"HKLM:\SOFTWARE\wow6432node\Microsoft\VisualStudio\SxS\VS7"

++++$msbuildPath+=+""

++++if+(Test-Path+$vs14key)+{
++++++++$key+=+Get-ItemProperty+$vs14key
++++++++$subkey+=+$key.MSBuildToolsPath
++++++++if+($subkey)+{
++++++++++++$msbuildPath+=+Join-Path+$subkey+"msbuild.exe"
++++++++}
++++}

++++if+(Test-Path+$vs15key)+{
++++++++$key+=+Get-ItemProperty+$vs15key
++++++++$subkey+=+$key."15.0"
++++++++if+($subkey)+{
++++++++++++$msbuildPath+=+Join-Path+$subkey+"MSBuild\15.0\bin\amd64\msbuild.exe"
++++++++}
++++}

++++return+$msbuildPath

}|code-block|syntax|javascript|1679642|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This works for Visual Studio 2015 and 2017:

<pre><code>function Get-MSBuild-Path {

 $vs14key = "HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0"
 $vs15key = "HKLM:\SOFTWARE\wow6432node\Microsoft\VisualStudio\SxS\VS7"

 $msbuildPath = ""

 if (Test-Path $vs14key) {
 $key = Get-ItemProperty $vs14key
 $subkey = $key.MSBuildToolsPath
 if ($subkey) {
 $msbuildPath = Join-Path $subkey "msbuild.exe"
 }
 }

 if (Test-Path $vs15key) {
 $key = Get-ItemProperty $vs15key
 $subkey = $key."15.0"
 if ($subkey) {
 $msbuildPath = Join-Path $subkey "MSBuild\15.0\bin\amd64\msbuild.exe"
 }
 }

 return $msbuildPath

}
</code></pre>

blocks|key|1679124|text|注册表位置|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1679125|HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5|code-block|syntax|javascript|1679126|提供可执行文件的位置。|1679127|但是，如果您需要保存任务扩展的位置，它是打开的|1679128|%25ProgramFiles%25\MSBuild|1679129|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The Registry locations 

<pre><code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5
</code></pre>

give the location for the executable.

But if you need the location where to save the Task extensions, it's on 

<pre><code>%ProgramFiles%\MSBuild
</code></pre>

blocks|key|1679702|text|从MSBuild+2017+(v15)开始，MSBuild现在安装在每个版本的Visual+Studio下的文件夹中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1679703|下面是在我的机器上找到MSBuild.exe的一些示例：|1679704|C:\windows\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe++(v2.0.50727.8745++32-bit)
C:\windows\Microsoft.NET\Framework64\v2.0.50727\MSBuild.exe++(v2.0.50727.8745++64-bit)
C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild.exe++(v3.5.30729.8763+32-bit)
C:\Windows\Microsoft.NET\Framework64\v3.5\MSBuild.exe++(v3.5.30729.8763+64-bit)
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe++(v4.7.2053.0+32-bit)
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe++(v4.7.2053.0+64-bit)
C:\Program+Files+(x86)\MSBuild\12.0\Bin\MSBuild.exe++(v12.0.21005.1+32-bit)
C:\Program+Files+(x86)\MSBuild\12.0\Bin\amd64\MSBuild.exe+(v12.0.21005.1+64-bit)
C:\Program+Files+(x86)\MSBuild\14.0\Bin\MSBuild.exe++(v14.0.25420.1+32-bit)
C:\Program+Files+(x86)\MSBuild\14.0\Bin\amd64\MSBuild.exe++(v14.0.25420.1+64-bit)
C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe++(v15.1.1012%2Bg251a9aec17+32-bit)
C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\BuildTools\MSBuild\15.0\Bin\amd64\MSBuild.exe+(v15.1.1012%2Bg251a9aec17+64-bit)
C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\{LicenceName}\MSBuild\Bin\MSBuild.exe+(v15.1.1012.6693+32-bit)
C:\Program+Files+(x86)\Microsoft+Visual+Studio\2017\{LicenceName}\MSBuild\Bin\amd64\MSBuild.exe+(v15.1.1012.6693+64-bit)|code-block|syntax|javascript|1679705|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Starting with MSBuild 2017 (v15), MSBuild is now installed in a folder under each version of Visual Studio

Here are some examples of where MSBuild.exe is found on my machine:

<pre><code>C:\windows\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe (v2.0.50727.8745 32-bit)
C:\windows\Microsoft.NET\Framework64\v2.0.50727\MSBuild.exe (v2.0.50727.8745 64-bit)
C:\Windows\Microsoft.NET\Framework\v3.5\MSBuild.exe (v3.5.30729.8763 32-bit)
C:\Windows\Microsoft.NET\Framework64\v3.5\MSBuild.exe (v3.5.30729.8763 64-bit)
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe (v4.7.2053.0 32-bit)
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe (v4.7.2053.0 64-bit)
C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe (v12.0.21005.1 32-bit)
C:\Program Files (x86)\MSBuild\12.0\Bin\amd64\MSBuild.exe (v12.0.21005.1 64-bit)
C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe (v14.0.25420.1 32-bit)
C:\Program Files (x86)\MSBuild\14.0\Bin\amd64\MSBuild.exe (v14.0.25420.1 64-bit)
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe (v15.1.1012+g251a9aec17 32-bit)
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\amd64\MSBuild.exe (v15.1.1012+g251a9aec17 64-bit)
C:\Program Files (x86)\Microsoft Visual Studio\2017\{LicenceName}\MSBuild\Bin\MSBuild.exe (v15.1.1012.6693 32-bit)
C:\Program Files (x86)\Microsoft Visual Studio\2017\{LicenceName}\MSBuild\Bin\amd64\MSBuild.exe (v15.1.1012.6693 64-bit)
</code></pre>

blocks|key|1464220|text|最简单的方法可能是打开PowerShell并输入|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1464221|dir+HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\|code-block|syntax|javascript|1464222|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

easiest way might be to open PowerShell and enter 

<pre><code>dir HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\
</code></pre>

blocks|key|1679590|text|在Windows+2003和更高版本上，在cmd中键入以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1679591|cmd>+where+MSBuild
Sample+result:+C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe|code-block|syntax|javascript|1679592|如果没有显示，则表示.NET框架未包含在系统路径中。MSBuild应与.NET编译器(vbc.exe、csc.exe)一起位于.NET安装文件夹中|1679593|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

On Windows 2003 and later, type this command in cmd:

<pre><code>cmd&gt; where MSBuild
Sample result: C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
</code></pre>

If nothing appears, it means that .NET framework is not included in the system PATH. The MSBuild should be in the .NET installation folder, along with .NET compilers (vbc.exe, csc.exe)

blocks|key|1464835|text|您可能不认为这里有太多要添加的内容，但也许是时候以一种统一的方式在所有版本之间实现这一点了。我将注册表查询方法(VS2015及以下版本)与vswhere+(VS2017及更高版本)的使用相结合，得出以下结论：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1464836|function+Find-MsBuild+{
++++Write-Host+"Using+VSWhere+to+find+msbuild..."
++++$path+=+&+$vswhere+-latest+-requires+Microsoft.Component.MSBuild+-find+MSBuild\**\Bin\MSBuild.exe+%7C+select-object+-first+1

++++if+(!$path)+{
++++++++Write-Host+"No+results+from+VSWhere,+using+registry+key+query+to+find+msbuild+(note+this+will+find+pre-VS2017+versions)..."
++++++++$path+=+Resolve-Path+HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\*+%7C
++++++++++++++++++++Get-ItemProperty+-Name+MSBuildToolsPath+%7C
++++++++++++++++++++sort+-Property+@{+Expression={+[double]::Parse($_.PSChildName)+};+Descending=$true+}+%7C
++++++++++++++++++++select+-exp+MSBuildToolsPath+-First+1+%7C
++++++++++++++++++++Join-Path+-ChildPath+"msbuild.exe"
++++}

++++if+(!$path)+{
++++++++throw+"Unable+to+find+path+to+msbuild.exe"
++++}

++++if+(!(Test-Path+$path))+{
++++++++throw+"Found+path+to+msbuild+as+$path,+but+file+does+not+exist+there"
++++}

++++Write-Host+"Using+MSBuild+at+$path..."
++++return+$path
}|code-block|syntax|javascript|1464837|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/vswhere^0|1X|7|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

You wouldn't think there's much to add here, but perhaps it's time for a unified way of doing this across all versions. I've combined the registry-query approach (VS2015 and below) with use of <a href="https://github.com/microsoft/vswhere" rel="nofollow noreferrer">vswhere</a> (VS2017 and above) to come up with this:

<pre><code>function Find-MsBuild {
 Write-Host "Using VSWhere to find msbuild..."
 $path = &amp; $vswhere -latest -requires Microsoft.Component.MSBuild -find MSBuild\**\Bin\MSBuild.exe | select-object -first 1

 if (!$path) {
 Write-Host "No results from VSWhere, using registry key query to find msbuild (note this will find pre-VS2017 versions)..."
 $path = Resolve-Path HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\* |
 Get-ItemProperty -Name MSBuildToolsPath |
 sort -Property @{ Expression={ [double]::Parse($_.PSChildName) }; Descending=$true } |
 select -exp MSBuildToolsPath -First 1 |
 Join-Path -ChildPath "msbuild.exe"
 }

 if (!$path) {
 throw "Unable to find path to msbuild.exe"
 }

 if (!(Test-Path $path)) {
 throw "Found path to msbuild as $path, but file does not exist there"
 }

 Write-Host "Using MSBuild at $path..."
 return $path
}
</code></pre>

blocks|key|1679765|text|对于Visual+Studio+2017，在不知道确切版本的情况下，可以在批处理脚本中使用以下代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1679766|FOR+/F+"tokens=*+USEBACKQ"+%25%25F+IN+(`where+/r+"%25PROGRAMFILES(x86)%25\Microsoft+Visual+
Studio\2017"+msbuild.exe+%5E%7C+findstr+/v+/i+"amd64"`)+DO+(SET+msbuildpath=%25%25F)|code-block|syntax|javascript|1679767|findstr命令用于忽略某些msbuild可执行文件(在本例中为amd64)。|1679768|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For Visual Studio 2017 without knowing the exact edition you could use this in a batch script:

<pre><code>FOR /F "tokens=* USEBACKQ" %%F IN (`where /r "%PROGRAMFILES(x86)%\Microsoft Visual 
Studio\2017" msbuild.exe ^| findstr /v /i "amd64"`) DO (SET msbuildpath=%%F)
</code></pre>

The findstr command is to ignore certain msbuild executables (in this example the amd64).

blocks|key|1464624|text|为https://github.com/linqpadless/LinqPadless/blob/master/build.cmd添加vswhere分支，在我的电脑上运行良好，vswhere分支在我伙伴的电脑上运行。也许，vswhere分支应该作为第一个检查向前移动。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1464625|@echo+off
setlocal
if+"%25PROCESSOR_ARCHITECTURE%25"=="x86"+set+PROGRAMS=%25ProgramFiles%25
if+defined+ProgramFiles(x86)+set+PROGRAMS=%25ProgramFiles(x86)%25
for+%25%25e+in+(Community+Professional+Enterprise)+do+(
++++if+exist+"%25PROGRAMS%25\Microsoft+Visual+Studio\2017\%25%25e\MSBuild\15.0\Bin\MSBuild.exe"+(
++++++++set+"MSBUILD=%25PROGRAMS%25\Microsoft+Visual+Studio\2017\%25%25e\MSBuild\15.0\Bin\MSBuild.exe"
++++)
)
if+exist+"%25MSBUILD%25"+goto+:build

for+/f+"usebackq+tokens=1*+delims=:+"+%25%25i+in+(`"%25ProgramFiles(x86)%25\Microsoft+Visual+Studio\Installer\vswhere.exe"+-latest+-requires+Microsoft.Component.MSBuild`)+do+(
++if+/i+"%25%25i"=="installationPath"+set+InstallDir=%25%25j
)

if+exist+"%25InstallDir%25\MSBuild\15.0\Bin\MSBuild.exe"+(
++set+"MSBUILD=%25InstallDir%25\MSBuild\15.0\Bin\MSBuild.exe"
)
if+exist+"%25MSBUILD%25"+goto+:build
set+MSBUILD=
for+%25%25i+in+(MSBuild.exe)+do+set+MSBUILD=%25%25~dpnx$PATH:i
if+not+defined+MSBUILD+goto+:nomsbuild
set+MSBUILD_VERSION_MAJOR=
set+MSBUILD_VERSION_MINOR=
for+/f+"delims=.+tokens=1,2,3,4"+%25%25m+in+('msbuild+/version+/nologo')+do+(
++++set+MSBUILD_VERSION_MAJOR=%25%25m
++++set+MSBUILD_VERSION_MINOR=%25%25n
)
echo+%25MSBUILD_VERSION_MAJOR%25+%25MSBUILD_VERSION_MINOR%25
if+not+defined+MSBUILD_VERSION_MAJOR+goto+:nomsbuild
if+not+defined+MSBUILD_VERSION_MINOR+goto+:nomsbuild
if+%25MSBUILD_VERSION_MAJOR%25+lss+15++++goto+:nomsbuild
if+%25MSBUILD_VERSION_MINOR%25+lss+1+++++goto+:nomsbuild
:restore
for+%25%25i+in+(NuGet.exe)+do+set+nuget=%25%25~dpnx$PATH:i
if+"%25nuget%25"==""+(
++++echo+WARNING!+NuGet+executable+not+found+in+PATH+so+build+may+fail!
++++echo+For+more+on+NuGet,+see+https://github.com/nuget/home
)
pushd+"%25~dp0"
popd
goto+:EOF

:build
setlocal
"%25MSBUILD%25"+-restore+-maxcpucount+%251+/p:Configuration=%252+/v:m+%253+%254+%255+%256+%257+%258+%259
goto+:EOF

:nomsbuild
echo+Microsoft+Build+version+15.1+(or+later)+does+not+appear+to+be
echo+installed+on+this+machine,+which+is+required+to+build+the+solution.
exit+/b+1|code-block|syntax|javascript|1464626|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/linqpadless/LinqPadless/blob/master/build.cmd^0|1|1S|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

add vswhere branch for <a href="https://github.com/linqpadless/LinqPadless/blob/master/build.cmd" rel="nofollow noreferrer">https://github.com/linqpadless/LinqPadless/blob/master/build.cmd</a>, works fine in my computer, and the vswhere branch works on my mate's computer.
May be, the vswhere branch should move forward as the first check.

<pre><code>@echo off
setlocal
if "%PROCESSOR_ARCHITECTURE%"=="x86" set PROGRAMS=%ProgramFiles%
if defined ProgramFiles(x86) set PROGRAMS=%ProgramFiles(x86)%
for %%e in (Community Professional Enterprise) do (
 if exist "%PROGRAMS%\Microsoft Visual Studio\2017\%%e\MSBuild\15.0\Bin\MSBuild.exe" (
 set "MSBUILD=%PROGRAMS%\Microsoft Visual Studio\2017\%%e\MSBuild\15.0\Bin\MSBuild.exe"
 )
)
if exist "%MSBUILD%" goto :build

for /f "usebackq tokens=1* delims=: " %%i in (`"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe" -latest -requires Microsoft.Component.MSBuild`) do (
 if /i "%%i"=="installationPath" set InstallDir=%%j
)

if exist "%InstallDir%\MSBuild\15.0\Bin\MSBuild.exe" (
 set "MSBUILD=%InstallDir%\MSBuild\15.0\Bin\MSBuild.exe"
)
if exist "%MSBUILD%" goto :build
set MSBUILD=
for %%i in (MSBuild.exe) do set MSBUILD=%%~dpnx$PATH:i
if not defined MSBUILD goto :nomsbuild
set MSBUILD_VERSION_MAJOR=
set MSBUILD_VERSION_MINOR=
for /f "delims=. tokens=1,2,3,4" %%m in ('msbuild /version /nologo') do (
 set MSBUILD_VERSION_MAJOR=%%m
 set MSBUILD_VERSION_MINOR=%%n
)
echo %MSBUILD_VERSION_MAJOR% %MSBUILD_VERSION_MINOR%
if not defined MSBUILD_VERSION_MAJOR goto :nomsbuild
if not defined MSBUILD_VERSION_MINOR goto :nomsbuild
if %MSBUILD_VERSION_MAJOR% lss 15 goto :nomsbuild
if %MSBUILD_VERSION_MINOR% lss 1 goto :nomsbuild
:restore
for %%i in (NuGet.exe) do set nuget=%%~dpnx$PATH:i
if "%nuget%"=="" (
 echo WARNING! NuGet executable not found in PATH so build may fail!
 echo For more on NuGet, see https://github.com/nuget/home
)
pushd "%~dp0"
popd
goto :EOF

:build
setlocal
"%MSBUILD%" -restore -maxcpucount %1 /p:Configuration=%2 /v:m %3 %4 %5 %6 %7 %8 %9
goto :EOF

:nomsbuild
echo Microsoft Build version 15.1 (or later) does not appear to be
echo installed on this machine, which is required to build the solution.
exit /b 1
</code></pre>

blocks|key|1464742|text|获取最新版本的MsBuild。最好的方式，对于所有类型的msbuild安装，对于不同的处理器架构(Power+Shell)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1464743|function+Get-MsBuild-Path
{
++++$msbuildPathes+=+$null
++++$ptrSize+=+[System.IntPtr]::Size
++++switch+($ptrSize)+{
++++++++4+{
++++++++++++$msbuildPathes+=
++++++++++++@(Resolve-Path+"${Env:ProgramFiles(x86)}\Microsoft+Visual+Studio\*\*\MSBuild\*\Bin\msbuild.exe"+-ErrorAction+SilentlyContinue)+%2B
++++++++++++@(Resolve-Path+"${Env:ProgramFiles(x86)}\MSBuild\*\Bin\MSBuild.exe"+-ErrorAction+SilentlyContinue)+%2B
++++++++++++@(Resolve-Path+"${Env:windir}\Microsoft.NET\Framework\*\MSBuild.exe"+-ErrorAction+SilentlyContinue)
++++++++}
++++++++8+{
++++++++++++$msbuildPathes+=
++++++++++++@(Resolve-Path+"${Env:ProgramFiles(x86)}\Microsoft+Visual+Studio\*\*\MSBuild\*\Bin\amd64\msbuild.exe"+-ErrorAction+SilentlyContinue)+%2B
++++++++++++@(Resolve-Path+"${Env:ProgramFiles(x86)}\MSBuild\*\Bin\amd64\MSBuild.exe"+-ErrorAction+SilentlyContinue)+%2B
++++++++++++@(Resolve-Path+"${Env:windir}\Microsoft.NET\Framework64\*\MSBuild.exe"+-ErrorAction+SilentlyContinue)
++++++++}
++++++++default+{
++++++++++++throw+($msgs.error_unknown_pointersize+-f+$ptrSize)
++++++++}
++++}

++++$latestMSBuildPath+=+$null
++++$latestVersion+=+$null
++++foreach+($msbuildFile+in+$msbuildPathes)
++++{
++++++++$msbuildPath+=+$msbuildFile.Path
++++++++$versionOutput+=+&+$msbuildPath+-version
++++++++$fileVersion+=+(New-Object+System.Version($versionOutput[$versionOutput.Length+-+1]))
++++++++if+(!$latestVersion+-or+$latestVersion+-lt+$fileVersion)
++++++++{
++++++++++++$latestVersion+=+$fileVersion
++++++++++++$latestMSBuildPath+=+$msbuildPath
++++++++}
++++}

++++Write-Host+"MSBuild+version+detected:+$latestVersion"+-Foreground+Yellow
++++Write-Host+"MSBuild+path:+$latestMSBuildPath"+-Foreground+Yellow

++++return+$latestMSBuildPath;
}|code-block|syntax|javascript|1464744|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Get latest version of MsBuild.
Best way, for all types of msbuild installation, for different processor architecture (Power Shell):

<pre><code>function Get-MsBuild-Path
{
 $msbuildPathes = $null
 $ptrSize = [System.IntPtr]::Size
 switch ($ptrSize) {
 4 {
 $msbuildPathes =
 @(Resolve-Path "${Env:ProgramFiles(x86)}\Microsoft Visual Studio\*\*\MSBuild\*\Bin\msbuild.exe" -ErrorAction SilentlyContinue) +
 @(Resolve-Path "${Env:ProgramFiles(x86)}\MSBuild\*\Bin\MSBuild.exe" -ErrorAction SilentlyContinue) +
 @(Resolve-Path "${Env:windir}\Microsoft.NET\Framework\*\MSBuild.exe" -ErrorAction SilentlyContinue)
 }
 8 {
 $msbuildPathes =
 @(Resolve-Path "${Env:ProgramFiles(x86)}\Microsoft Visual Studio\*\*\MSBuild\*\Bin\amd64\msbuild.exe" -ErrorAction SilentlyContinue) +
 @(Resolve-Path "${Env:ProgramFiles(x86)}\MSBuild\*\Bin\amd64\MSBuild.exe" -ErrorAction SilentlyContinue) +
 @(Resolve-Path "${Env:windir}\Microsoft.NET\Framework64\*\MSBuild.exe" -ErrorAction SilentlyContinue)
 }
 default {
 throw ($msgs.error_unknown_pointersize -f $ptrSize)
 }
 }

 $latestMSBuildPath = $null
 $latestVersion = $null
 foreach ($msbuildFile in $msbuildPathes)
 {
 $msbuildPath = $msbuildFile.Path
 $versionOutput = &amp; $msbuildPath -version
 $fileVersion = (New-Object System.Version($versionOutput[$versionOutput.Length - 1]))
 if (!$latestVersion -or $latestVersion -lt $fileVersion)
 {
 $latestVersion = $fileVersion
 $latestMSBuildPath = $msbuildPath
 }
 }

 Write-Host "MSBuild version detected: $latestVersion" -Foreground Yellow
 Write-Host "MSBuild path: $latestMSBuildPath" -Foreground Yellow

 return $latestMSBuildPath;
}
</code></pre>

blocks|key|1464671|text|如果你喜欢冒险，你也可以在https://github.com/Microsoft/msbuild/releases/上从GitHub获得MsBuild的源代码和最新版本|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1464672|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Microsoft/msbuild/releases/^0|D|1A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you are adventurous you can also get the source code and latest release of MsBuild from GitHub now at <a href="https://github.com/Microsoft/msbuild/releases/" rel="nofollow noreferrer">https://github.com/Microsoft/msbuild/releases/</a>

How can I programatically get the path to MSBuild from a machine where my .exe is running?

I can get the .NET version from the Environment but is there a way of getting the correct folder for a .NET version?

Path to MSBuild

如何从运行.exe的机器上以编程方式获取MSBuild的路径？我可以从环境中获取.NET版本，但是有没有方法可以为.NET版本获取正确的文件夹？

问MSBuild的路径
EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MSBuild的路径EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MSBuild的路径
EN