Comments on: Another hidden .Net Tool usage basics: ilMerge http://www.canerten.com/another-hidden-net-tool-usage-basics-ilmerge/ Adventures in Computing - Can Erten's Blog Thu, 28 Aug 2008 19:28:32 +0000 http://wordpress.org/?v=2.6.1 By: Yonatan Leonov http://www.canerten.com/another-hidden-net-tool-usage-basics-ilmerge/#comment-26948 Yonatan Leonov Mon, 07 Jan 2008 11:04:55 +0000 http://www.canerten.com/another-hidden-net-tool-usage-basics-ilmerge/#comment-26948 ILMerge is helpfull in some scenarios, but with others it can be dangerous. For example - if you merge 2 assemblies with the same non public type on both - it will work but will change the name of the type. is it a problem? yes if you use reflection... and you can end up with multiple instance of a singleton too. don't forget the memory footprint of the merged assembly. so do use this tool, but only after you understand the implications. read more on <a href="http://readcommit.blogspot.com/2007/12/referencing-two-different-version-of.html" rel="nofollow">Referencing different versions of an assembly - Part 1 (ILMerge)</a> ILMerge is helpfull in some scenarios, but with others it can be dangerous.

For example - if you merge 2 assemblies with the same non public type on both - it will work but will change the name of the type.

is it a problem? yes if you use reflection…

and you can end up with multiple instance of a singleton too.

don’t forget the memory footprint of the merged assembly.

so do use this tool, but only after you understand the implications.

read more on Referencing different versions of an assembly - Part 1 (ILMerge)

]]>