Problem
You have a .NET application that uses multiple assemblies but you want it as a single executable.
Solution
Use ILMerge to merge the assemblies into one executable.
Solution (with WPF support)
Embed the required assemblies as embedded resources in your project and extend the assembly resolving to check the embedded resources (see second link for details).
Hint
If you build an executable that contains something like a common namespace, that is also used in other applications, and the other applications also reference the single executable there will be a namespace clash. To avoid this you can use the /internalize parameter of ILMerge (see first link for details).
Links
- http://www.bjoernrochel.de/2009/07/07/how-to-shoot-yourself-in-the-foot-with-ilmerge/
- http://blogs.msdn.com/b/microsoft_press/archive/2010/02/03/jeffrey-richter-excerpt-2-from-clr-via-c-third-edition.aspx
- http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx
- http://www.microsoft.com/en-us/download/details.aspx?id=17630
Leave a Reply