MSBuild - Morten Nielsen

Morten Nielsen

Sign in Subscribe

MSBuild

A collection of 6 posts

MSBuild fails to compile WPF with: error MC2000: Unkown build error '…' does not have an implementation

My initial solution in this post was WRONG, it just changed the compile order of our build which made the error occur later after other issues were resolved. I’ve updated the post accordingly. I’m sorry if anyone had to read this post twice. We have been struggling with

Independent trunk and MSBuild

A while back I posted a post about a concept I call the Independent trunk [https://www.morkeleb.com/2008/07/independent-trunk-manging-source.html]. The core concept is that everything required to build a distributable version of a software product is checked in under one branch in the source-control system. A

Safe import of .target files

We’ve changed most of our projects to import other .target files. This means that we get allot of warnings about unsafe imports. To eliminate these we can add a registry setting with the file name of the .targets file in HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\9.0\MSBuild\

error MSB3491: Could not write lines to file (Solution).(Configuration).vsprops

Just got this error message from MSBuild. I’ve gotten it before, but I couldn’t remember what the problem was. Build FAILED. “D:\Builds*\BuildType\TFSBuild.proj” (EndToEndIteration target) (1) ->“D:\Builds*\BuildType\TFSBuild.proj” (CoreCompile target) (1:2) ->“D:\Builds*\BuildType\TFSBuild.proj” (CompileConfiguration target) (1:

Balancing builds over several build servers

I always have a tendency to strive to find uses for the academic problem solving techniques I learned when I achieved my masters. This is something that is a bit fun, doesn’t take too long and gives a quick starting template for balancing builds over several build agents in

Running tests in DesktopBuild

This post is inspired by a problem we had in our TFS2008 build environment, I am not sure if it applies to the 2005 version of MSBuild. The problem Say you are running tests in your team builds, and you have configured your build so they can run on a