<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Build - Tag - Joel Beckham</title><link>http://example.org/tags/build/</link><description>Build - Tag - Joel Beckham</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 18 Jan 2012 00:00:00 +0000</lastBuildDate><atom:link href="http://example.org/tags/build/" rel="self" type="application/rss+xml"/><item><title>Sharing Build Configuration Settings Between Project Files</title><link>http://example.org/posts/2012/2012-01-18-sharing-build-configuration-settings-between-project-files/</link><pubDate>Wed, 18 Jan 2012 00:00:00 +0000</pubDate><author>jbeckham</author><guid>http://example.org/posts/2012/2012-01-18-sharing-build-configuration-settings-between-project-files/</guid><description>Update: Oh snap… nCrunch isn&amp;rsquo;t smart enough to pull in the external configurations like this, and so it won&amp;rsquo;t run any of my tests. Gotta find plan B.
As we&amp;rsquo;ve added new projects to our solution and new build environments, it has become increasingly difficult to maintain consistency in our settings across all projects. Here is how we addressed it.
Added a new MSBuild target file (CommonBuildConfigurationSettings.target) to the solution to contain these settings.</description></item></channel></rss>