For precise semantic code complete, you need compile_commands.json for YouCompleteMe(also RTags) which records compile flags for every source file. bear or btrace can generate compile_commands.json from existng none-CMake based project (mostly for UNIX-liked OS). And this modified MSBuild is for existing MSVC based project(mostly for Windows).

msbuild project in memory is built up by manyu 'task', Microsof.Build.CPPTasks.CL is just for compiling, this components is not open sourced, but its most important logic is just in base class ToolTask (which is part of Opensourced msbuild).this mod just hook into ToolTask, ignore none-CL task(no help),ignoer skip-rebuild-check(you can still get flags even if project is built), skip actually build command, and write a compile_commands.json in msbuild current working directory. for use with clang ,this adds "--driver-mode=cl" to every commands

YouCompleteMe throws msvc style parameters incorrectly .you need YouCompleteMe with ycmd replaced third_party/ycmd . And you need to build newest clang, not the one YouCompleteMe auto downloaded (clang has bug that can not found include path, fixed in 277005 but not 3.9 binary release)

just build as original msbuild (following), some tips:

1. Choose x86 configuration. x64 will gives 'dll can not load'(I'm not familiar with dotnet and I don't know why).
2. Build whole soluation, not only msbuild project. some basic task defined in other projects is not built as msbuild's dependencies.
3. Now you can run this msbuild, but it will lookup tracker.exe in same directory (which built msbuild.exe in). you need to copy it (mostly under C:\program files(x86)\msbuild\14.0\bin depends on your bitness or version) to directory which your built msbuild.exe in. you must copy correct bitness version (you build x86 version msbuild, so copy x86 version tracker.exe).
4. tracker.exe will load FileTracker32/64.dll in same directory ,so you must also copy these files. I'm lasy, so I just copy everything none-conflict from C:\Program Files (x86)\MSBuild\14.0\Bin
5. now you can run this msbuild to build your project or soluation, it will gives compile_commads.json in current working dir.

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 does not depend on Visual Studio. By invoking msbuild.exe on your project or solution file, you can orchestrate and build products in environments where Visual Studio isn't installed.

For more information on MSBuild, see the MSDN documentation.

Full framework build from master (stable, inserted into Visual Studio builds):

The xplat branch is soon to be merged back upstream. Follow the The Great Merge milestone for progress.

Runtime\OS	Windows	Ubuntu	Mac OS X
Full Framework		N/A	N/A
.NET Core

• Clone the sources: git clone https://github.com/Microsoft/msbuild.git

For the full supported experience, you will need to have Visual Studio 2015. You can open the solution in Visual Studio 2013, but you will encounter issues building with the provided scripts.

To get started on Visual Studio 2015:

1. Install Visual Studio 2015. Select the following optional components:

• Microsoft Web Developer Tools
• Universal Windows App Development Tools
  • Tools and Windows SDK 10.0.10240

2. Clone the source code (see above).
3. Restore NuGet packages: msbuild /t:BulkRestoreNugetPackages build.proj
4. Open src/MSBuild.sln solution in Visual Studio 2015.

MSBuild's xplat branch allows MSBuild to be run on Unix Systems. Set-up instructions can be viewed on the wiki: Building Testing and Debugging on .Net Core MSBuild

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Before you contribute, please read through the contributing and developer guides to get an idea of what kinds of pull requests we will or won't accept.

• Contributing Guide
• Developer Guide

Want to get more familiar with what's going on in the code?

• Pull requests: Open/Closed
• Issues

You are also encouraged to start a discussion by filing an issue or creating a gist.

• MSBuild. Microsoft.Build.CommandLine is the entrypoint for the Microsoft Build Engine (MSBuild.exe).

• Microsoft.Build. The Microsoft.Build namespaces contain types that provide programmatic access to, and control of, the MSBuild engine.

• Microsoft.Build.Framework. The Microsoft.Build.Framework namespace contains the types that define how tasks and loggers interact with the MSBuild engine. For additional information on this component, see our Microsoft.Build.Framework wiki page.

• Microsoft.Build.Tasks. The Microsoft.Build.Tasks namespace contains the implementation of all tasks shipping with MSBuild.

• Microsoft.Build.Utilities. The Microsoft.Build.Utilities namespace provides helper classes that you can use to create your own MSBuild loggers and tasks.

MSBuild is licensed under the MIT license.