This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
|Stable release||2015 (14.0.23107.10) / 10 July 2015|
Microsoft Build Tools (also known as MSBuild and Microsoft Build Engine) is a build tool set for managed code as well as native C++ code and was part of .NET Framework. Visual Studio depends on MSBuild, but MSBuild does not depend on Visual Studio. Visual Studio Application Lifecycle Management depends on MSBuild to perform team builds via the Team Foundation Server.
MSBuild is a build tool that helps automate the process of creating a software product, including compiling the source code, packaging, testing, deployment and creating documentations. With MSBuild, it is possible to build Visual Studio projects and solutions without the Visual Studio IDE installed. MSBuild is available at no cost. MSBuild was previously bundled with .NET Framework; starting with Visual Studio 2013, however, it is bundled with Visual Studio instead. MSBuild is a functional replacement for the nmake utility, the latter of which remains in use in projects that originated in older Visual Studio releases.
MSBuild acts on MSBuild project files which have a similar XML syntax to Apache Ant or NAnt. Even though the syntax is based upon well-defined XML schema, the fundamental structure and operation is comparable to the traditional Unix make utility: the user specifies what will be used (typically source code files) and what the result should be (typically an application), but the utility itself decides what to do and the order in which to do it.
MSBuild can build a project against a supported .NET Framework version of choice. This feature is called "multitargeting". Any given build of a project, however, can only target one version of the framework at a time.
||This section may be confusing or unclear to readers. In particular, it is unclear what this section is talking about and what is the nature of, say, a "Target" or "Task". Examples would help. (April 2013) (Learn how and when to remove this template message)|
- A Target contains a set of tasks for MSBuild to execute. The focus of MSBuild is the result Target specified when invoking MSBuild with the project file. This is because a Project may contain several Target entries, each executed sequentially (and conditionally). Subsequent dependent Targets are executed before the requested Target. The execution flow of the current Target can be directed using the following attributes: Condition, BeforeTargets, AfterTargets, & DependsOnTargets. Each Target may be self-contained with the necessary Tasks to complete itself. A Target is typically an action executed on a file, set of files or directory.
- A Task is a command which is executed in order to complete a Target. Tasks are used to group and execute any number of actions during the build process. They are typically implemented in a .NET assembly as a class which inherits from the Task class or implements the ITask interface. Many basic tasks are shipped as part of the .NET Framework, and community developed tasks are freely available. Some examples of Tasks include copying files, creating directories, or parsing XML.
- Properties and Items
- MSBuild provides Properties and Items, which are conceptually equivalent to make's macros. Properties specify static values, whereas Items are usually used to define sets of files or folders on which to perform Tasks. Specifying files on Items is made easy by the support of wildcards.
- "Microsoft Build Tools 2015". Download Center. Microsoft. 10 July 2015.
- "MSBuild". MSDN. Microsoft. Retrieved 11 December 2013.
- "Microsoft Build Tools". Download Center. Microsoft. 10 July 2015. Retrieved 11 September 2015.
- "What's New in MSBuild 12.0". MSDN. Microsoft. Retrieved 10 March 2014.
- "MSBuild Multitargeting Overview". MSDN. Microsoft. Retrieved 11 December 2013.
- "MSBuild Task Reference". MSDN. Microsoft. Retrieved 11 March 2015.
- Kretzler, Brian (2011). MSBuild Trickery: 99 Ways to Bend the Build Engine to Your Will. K Cross Seven Ranch Company. p. 426. ISBN 978-0-615-50907-5.
- Hashimi, Sayed Ibrahim; Bartholomew, William (2009). Inside the Microsoft Build Engine: Using MSBuild and Team Foundation Build. Microsoft Press. p. 406. ISBN 978-0-7356-2628-7.
- Hashimi, Sayed Ibrahim (June 2006). "Inside MSBuild: Compiling Apps With Custom Tasks For The Microsoft Build Engine". MSDN Magazine (Microsoft). Retrieved 11 April 2013.
- Hashimi, Sayed Ibrahim (March 2007). "WiX Tricks: Automate Releases With MSBuild And Windows Installer XML". MSDN Magazine (Microsoft). Retrieved 11 April 2013.
- Hashimi, Sayed Ibrahim (February 2009). "MSBuild: Best Practices For Creating Reliable Builds, Part 1". MSDN Magazine (Microsoft). Retrieved 11 April 2013.
- Hashimi, Sayed Ibrahim (March 2009). "MSBuild: Best Practices For Creating Reliable Builds, Part 2". MSDN Magazine (Microsoft). Retrieved 11 April 2013.
- Reif, Andreas (10 June 2010). "Einführung in Microsofts Build-Management-Technik MSBuild" [Introduction to Microsoft's build management technology, MSBuild]. heise Developer (in German). Heinz Heise. Retrieved 11 April 2013.
- MSBuild Reference on Microsoft Developer Network
- Team Foundation Build overview on Microsoft Developer Network
- MSBuild Extension Pack on CodePlex
- MSBuild Launch Pad (mPad) on CodePlex
- MSBuild Shell Extension on GitHub
- Open Source MSBuild Community Tasks Project on GitHub
- MSBuild Target Framework and Target Platform on Microsoft Developer Network
- Open Source MSBuild on GitHub
- Announcement on the release of MSBuild as Open Source