Menu
I noticed when Visual Studio 2012 RTM was closed, that many instances of MsBuild.exe are still in memory.
Why ?
543
For a typical default installation on Windows 10, MSBuild.exe is under the installation folder in MSBuild\Current\Bin.
The Microsoft Build Engine is a platform for building applications. This engine, which is also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software. Visual Studio uses MSBuild, but MSBuild doesn't depend on Visual Studio.
Visual Studio determines the build order and calls into MSBuild separately (as needed), all completely under Visual Studio's control. Another difference arises when MSBuild is invoked with a solution file, MSBuild parses the solution file, creates a standard XML input file, evaluates it, and executes it as a project.
MSBuild 4.5 is still part of the . NET 4.5. 1 Framework. The Framework's MSBuild will still be used by Visual Studio 2012, and is able to build any projects that round trip from Visual Studio 2013 to Visual Studio 2012.
The MSBuild processes are kept running for a period of time (fifteen minutes, I believe) after Visual Studio is closed. This is an attempt to improve performance, the idea being that idle MSBuild processes could be reused if another build is kicked off soon and the overhead of spawning a new process can be eliminated.
You can disable this by setting an environment variable MSBUILDDISABLENODEREUSE=1 (before starting VS) or specifying /nodeReuse:false (or /nr:false) if building from the command line.
Related issues filed on MSConnect:
155
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
