ILMerge allows developers to combine several .NET Assemblies into a single executable. The most obvious advantage of this is in deployment scenarios where the ability to copy a single file is preferable.
ILMerge is a Microsoft Research project dating back to 2004. Unlike most MS Research projects, this one is licensed for commercial use.
ILMerge can be used on all versions of the framework. PDB files can be merged, but only for 2.0 assemblies. The ASP.Net utility, aspnet_merge, is based on this project.
This release focused mainly on bug fixes, especially for generics.
/filters:no_upscale()/sponsorship/topic/bf6d91ca-0f85-438b-90a2-3caa0794034e/ProgressLogoRSB-1635398897145.png)
/articles/anomaly-detection-ml-net/en/smallimage/Anomaly-detection- using-ML-NET-small-image-1635501624459.jpg)
/articles/microservices-concepts-patterns/en/smallimage/Microservices-the-letter-and-the-spirit-small-image-1637327649178.jpg)
/articles/overriding-sealed-methods-c-sharp/en/smallimage/logo-1636574154697.jpg){kind=logo}
/articles/records-c9-tugce-ozdeger/en/smallimage/logo-1635178528926.jpg){kind=logo}
/articles/xamarin-community-toolkit-gerald-versluis/en/smallimage/present-future-xamarin-community-toolkit-Gerald-Versluis-small-image-1634205586181.jpg)
/articles/Testing-With-Persistence-Layers/en/smallimage/logo-1633708798190.jpg){kind=logo}
/presentations/piranha-refactoring/en/smallimage/Murali Krishna Ramanathan-s-1637910977077.jpg)
/articles/testing-blockchain-solutions/en/smallimage/logo-1637008540204.jpg){kind=logo}
/presentations/devsecops-governance-practices-tools/en/smallimage/Mario-Platt-s-1636028918566.jpg)
/presentations/reliability-custom-tools/en/smallimage/Daniel Hochman-s-1627545234166.jpg)
/articles/paving-road-production-coinbase/en/smallimage/logo copy-1625496407849.jpg)
/articles/agile-team-maturity-assessment/en/smallimage/1G_yz7zg-1624490275821.jpg)
/articles/validation-autonomous-systems/en/smallimage/logo-1624226498499.jpg){kind=logo}
/articles/mindmap-driven-testing/en/smallimage/mind-map-guidelines-1623391386570.jpg)
/articles/java-release-management-with-jreleaser/en/smallimage/java-logo-1623246269622.jpg){kind=logo}
/articles/introducing-kivakit/en/smallimage/logo-1637780334611.jpg){kind=logo}
/presentations/data-mesh-concepts/en/smallimage/Zhamak-Dehghani-s-1637910615302.jpg)
/presentations/sre-apprentices/en/smallimage/Tammy-Butow-chaos-engineering-resilience-logo-1637911153639.jpeg){kind=logo}
/articles/agile-coaches-guides-others/en/smallimage/logo-1637688009643.jpg){kind=logo}
/articles/design-thinking-organizational-change/en/smallimage/logo-1637326427990.jpg){kind=logo}
/presentations/java-update-versions/en/smallimage/Marc_Hoffmann-s-1637581262221.jpg)
/presentations/silo-systems-streaming-data/en/smallimage/ricardo-ferreira-s-1637313220787.jpg)
/articles/financial-software-low-code/en/smallimage/logo-1637135531983.jpg){kind=logo}
/presentations/team-topologies-technical-agility/en/smallimage/team-topologies-s-1637581522204.jpg)
Community comments
Would improved performance be another advantage?
by Eric Smith,
Would improved performance be another advantage?
by Eric Smith,
Your message is awaiting moderation. Thank you for participating in the discussion.
I had just been wondering yesterday if many small assemblies or fewer large assemblies was a better approach. I saw a blog posting by Brad Abrams (blogs.msdn.com/brada/archive/2004/0505/126934.aspx) that indicates that fewer large assemblies should perform better. Presumably those gains could be had by using ILMerge even if it were convenient to develop using smaller assemblies.