Title: MSBuild
Subject: Comparison of continuous integration software, FinalBuilder, Microsoft Visual Studio, Visual Studio Lab Management, Monobjc
Microsoft Build Tools
2015 (14.0.23107.10) / 10 July 2015 (2015-07-10)[1]
Written in
Build tool
/msbuild/microsoft.comgithub
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.[2] Visual Studio Application Lifecycle Management depends on MSBuild to perform team builds via the Team Foundation Server.[2]
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.[3] MSBuild was previously bundled with .NET Framework; starting with Visual Studio 2013, however, it is bundled with Visual Studio instead.[4] 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.[5]
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,[6] 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.
List of build automation software
^ a b
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
msbuildbook.com
Open Source MSBuild on GitHub
Announcement on the release of MSBuild as Open Source
Articles with topics of unclear notability from December 2013
All articles with topics of unclear notability
Articles needing additional references from December 2013
Compiling tools
Mono (software), Asp.net, Windows 8, Microsoft, Source code
Google, Apple Inc., Samsung Electronics, Microsoft Office, Sony
Compiler, Machine code, Programmer, Linux, Java (programming language)
Comparison of continuous integration software
Proprietary software, GitHub, E-mail, Rss, Python (programming language)
FinalBuilder
.NET Framework, Continuous Integration, VSoft Technologies, Gui, Borland Delphi
Visual Studio Lab Management
Microsoft, .NET Framework, Visual Studio Application Lifecycle Management, System Center Virtual Machine Manager, Microsoft Visual Studio