Foreword
Automated build systems are the workhorses of the software development team. They tirelessly do what they are told. They get. They clean. They build. They rebuild. They copy. They deploy. They test. And they don’t judge those who break the build. Without emotion, they just do what they are told. We can’t live without them.
The problem is that an automated build system such as this can be more difficult to construct than the underlying application the team really cares about. Why is this? From my experience, it’s caused by several factors. MSBuild is not widely understood and is quite complex. There are no IDEs that support a visual "drag and drop" editing and debugging experience. Most teams don’t have a dedicated "build master" to learn ...
Get Inside the Microsoft® Build Engine: Using MSBuild and Team Foundation Build now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
