http://blogs.msdn.com/b/jomo_fisher/archive/2006/03/05/ilmerge-in-msbuild.aspx&lt;!-- Use of included script samples are subject to the terms specified at http://www.microsoft.com/resources/sharedsource/licensingbasics/permissivelicense.mspx Written by Jomo Fisher --&gt; &lt;Project DefaultTargets="Build" xmlns=" http://schemasen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/jomo_fisher/archive/2006/03/05/ilmerge-in-msbuild.aspx#9940931Thu, 24 Dec 2009 11:42:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:9940931Daniel Fortunov<p>I realise this is just something you came up in your spare time but one shortcoming is that this task will execute on every build because there is no InputFiles/OutputFiles specified for the task.</p> <p>Furthermore, specifying these values correctly is tricky because you're overwriting an existing build output file when you do the ILMerge, so if you're not careful you could get into a position where the task never runs because it sees the (non-yet-merged) output file is up to date!</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9940931" width="1" height="1">http://blogs.msdn.com/b/jomo_fisher/archive/2006/03/05/ilmerge-in-msbuild.aspx#544146Mon, 06 Mar 2006 01:33:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:544146Jomo FisherJomo Fisher--Over the last few years I've been coding mostly in C#--before that, my day-to-day work was...<img src="http://blogs.msdn.com/aggbug.aspx?PostID=544146" width="1" height="1">