MSBuild is abuild tool that helps automate the process of creating a software product, includingcompiling thesource code,packaging, testing,deployment and creating documentations. With MSBuild, it is possible to build Visual Studio projects and solutions without the Visual StudioIDE installed. MSBuild isfree and open-source.[5] MSBuild was previously bundled with.NET Framework; starting withVisual Studio 2013, however, it is bundled with Visual Studio instead.[6] MSBuild is a functional replacement for thenmake utility, which remains in use in projects that originated in older Visual Studio releases.
MSBuild acts on MSBuild project files which have a similarXML syntax toApache Ant orNAnt. Even though the syntax is based upon well-definedXML schema, the fundamental structure and operation is comparable to the traditional Unixmake utility: the user specifies what will be used (typically source code files) and what the result should be (typically a static library, DLL or an executable application), but the utility itself decides what to do and the order in which to carry out the build.
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.[7]
ATarget contains a set of tasks for MSBuild to execute. The focus of MSBuild is the resultTarget specified when invoking MSBuild with the project file. This is because aProject may contain severalTarget entries, each executed sequentially (and conditionally). Subsequent dependent Targets are executed before the requested Target. The execution flow of the currentTarget 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.
Task
ATask 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,[14] and community developed tasks are freely available. Some examples ofTasks include copying files, creating directories, or parsing XML.
Properties and Items
MSBuild providesProperties andItems, which are conceptually equivalent tomake'smacros. 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.
^Hashimi, Sayed Ibrahim; Bartholomew, William (2009).Inside the Microsoft Build Engine: Using MSBuild and Team Foundation Build. Microsoft Press. p. 406.ISBN978-0-7356-2628-7.