Skip to content

Building-Testing-and-Debugging-on-.Net-Core-MSBuild.md

Latest commit

 

History

History
47 lines (24 loc) · 2.53 KB

Building-Testing-and-Debugging-on-.Net-Core-MSBuild.md

File metadata and controls

47 lines (24 loc) · 2.53 KB

MSBuild can be successfully built on Windows, OS X 10.13, Ubuntu 14.04, and Ubuntu 16.04.

Windows

Build

build.cmd -msbuildEngine dotnet

Unix

The easy way

Install the latest .NET Core SDK from http://dot.net/core. That will ensure all prerequisites for our build are met.

Manually installing required packages for OSX & Ubuntu

.NET Core prerequisites.

  • OpenSSL: MSBuild uses the .Net CLI during its build process. The CLI requires a recent OpenSSL library available in /usr/lib. This can be downloaded using brew on OS X (brew install openssl) and apt-get (apt-get install openssl) on Ubuntu, or building from source. If you use a different package manager and see an error that says Unable to load DLL 'System.Security.Cryptography.Native', dotnet may be looking in the wrong place for the library.

Build

./build.sh

If you encounter errors, see Something's wrong in my build

Tests

./build.sh --test

Getting .Net Core MSBuild binaries without building the code

The best way to get .NET Core MSBuild is by installing the .NET Core SDK, which redistributes us. This will get you the latest released version of MSBuild for .NET Core. After installing it, you can use MSBuild through dotnet build or by manual invocation of the MSBuild.dll in the dotnet distribution.

Debugging

Wait in Main

Set the environment variable MSBUILDDEBUGONSTART to 2, then attach a debugger to the process manually after it starts.

Using the repository binaries to perform builds

To build projects using the MSBuild binaries from the repository, you first need to do a build (command: build.cmd /p:CreateBootstrap=true) which produces a bootstrap directory mimicking a Visual Studio (full framework flavor) or dotnet CLI (.net core flavor) installation.

Now, just point dotnet ./artifacts/bin/bootstrap/netcoreapp2.1/MSBuild/MSBuild.dll at a project file.

Alternatively, if you want to test the msbuild binaries in a more realistic environment, you can overwrite the dotnet CLI msbuild binaries (found under a path like ~/dotnet/sdk/3.0.100-alpha1-009428/) with the msbuild binaries from the above bootstrap directory. You might have to kill existing dotnet processes before doing this. Then, (using the previous dotnet example directory) just point ~/dotnet/dotnet build at a project file.