Click here to Skip to main content
15,177,810 members
Articles / Operating Systems / Windows
Posted 21 Jan 2005


108 bookmarked

Merging .NET assemblies using ILMerge

Rate me:
Please Sign up or sign in to vote.
4.68/5 (57 votes)
21 Jan 20053 min read
Shows how to merge multiple .NET assemblies to a single one using ILMerge.


As you know, traditional linking of object code is no longer necessary in .NET. A .NET program will usually consist of multiple parts. A typical .NET application consists of an executable assembly, a few assemblies in the program directory, and a few assemblies in the global assembly cache. When the program is run, the runtime combines all these parts to a program. Linking at compile time is no longer necessary.

But sometimes, it is nevertheless useful to combine all parts a program needs to execute into a single assembly. For example, you might want to simplify the deployment of your application by combining the program, all required libraries, and all resources, into a single .exe file.

A single project

If all parts of your program are written by yourself in the same language, you can obviously just add all source files to a single project. The result will be a single DLL or EXE containing all dependencies.

csc /target:winexe /out:Program.exe 
      MainProgram.cs ClassLibrary1.cs ClassLibrary2.cs

However, if your program is written in multiple languages or if you are using binary third party libraries, you are out of luck.

.NET Modules

The .NET compilers already contain options for exactly this. If you compile a project, there is an option to create a module, which is similar to an assembly but without a manifest file. You can then use the al.exe tool to combine some of these modules to a single assembly. This feature makes it possible to create a single assembly that contains multiple languages.

First, you would compile the program and the class libraries to netmodules using the module target. Then you can use the assembly linker al.exe to combine these modules to a single assembly.

csc /target:module /out:ClassLibrary1.netmodule ClassLibrary1.cs
vbc /target:module /out:ClassLibrary2.netmodule ClassLibrary2.vb
vbc /target:module /out:Program.netmodule Program.vb
al /target:winexe /out:Program.exe ClassLibrary1.netmodule 
                 ClassLibrary2.netmodule Program.netmodule

But unfortunately, this method only works if you have all the required parts of your program either as source code or as .NET modules. If you are useing a third party class library in assembly form, you are again out of luck.


Since a .NET module is basically just an assembly without an assembly manifest, it should be possible to convert an assembly to a .NET module, at least that is what I thought. When researching this on Google, I found a tremendously useful tool on Microsoft research called ILMerge. This little gem makes it possible to link multiple assemblies to a single one.

First, you would compile your libraries to DLLs and your program to an EXE referencing the DLLs. This is exactly what Visual Studio would do if you had multiple libraries and a program referencing these libraries, so there is no need to do this on the command line.

csc /target:library /out:ClassLibrary1.dll ClassLibrary1.cs
vbc /target:library /out:ClassLibrary2.dll ClassLibrary2.vb
vbc /target:winexe /out:Program.exe 
    /reference:ClassLibrary1.dll,ClassLibrary2.dll Program.vb

This will produce a normal .exe that requires the two DLLs in the program directory or in the global assembly cache to run.

Now you can link these parts to a single self-contained EXE, using ILMerge:

ilmerge /target:winexe /out:SelfContainedProgram.exe 
        Program.exe ClassLibrary1.dll ClassLibrary2.dll

The nice thing about this is that you can also merge third party assemblies like commercial class libraries into your program. And you do not have to modify your build process. All you have to do is to merge the assemblies to a single EXE before deploying.


I found ILMerge tremendously useful, and I think that something like this should be a part of the .NET framework SDK. Maybe just enhance al.exe so that it can also link DLLs.

I have only scratched the surface of the .NET build process and the capabilities of ILMerge, and this article might contain many inaccuracies or even errors. But I found ilmerge.exe so useful that I just had to write about it.


  • ILMerge: The ILMerge utility from Michael Barnett of Microsoft Research.
  • ILMerge Task: A NAnt task for ILMerge.


This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


About the Author

Rüdiger Klaehn
Web Developer
Germany Germany
Rüdiger Klaehn works as freelance developer in the space industry. He is very interested in functional programming languages and hopes that .NET will lead to a more widespread adoption in the industry.

Comments and Discussions

QuestionLink for ILMerge Needs to be Updated Pin
Jim Fell25-Jul-19 8:54
MemberJim Fell25-Jul-19 8:54 
QuestionIs there any possibility to merge a Net module file and DLL?? Pin
ahamednafeel19-May-15 18:39
Memberahamednafeel19-May-15 18:39 
QuestionIlmerge creating extra name spaces Pin
Member 1110029222-Sep-14 2:34
MemberMember 1110029222-Sep-14 2:34 
Questionwhere does coding go Pin
Conor Penhale28-May-14 20:32
MemberConor Penhale28-May-14 20:32 
GeneralMy vote of 4 Pin
Lagkip14-Dec-12 5:13
MemberLagkip14-Dec-12 5:13 
QuestionLinking assemblies AND .net framework into one assembly using FuZe Pin
Frank van Bokhoven20-Sep-12 4:10
MemberFrank van Bokhoven20-Sep-12 4:10 
SuggestionILMerge Pin
Mast Avalons6-Dec-11 9:33
MemberMast Avalons6-Dec-11 9:33 
GeneralRe: ILMerge Pin
Bartosz Wójcik27-Jan-12 5:15
MemberBartosz Wójcik27-Jan-12 5:15 
GeneralMy vote of 5 Pin
Mast Avalons6-Dec-11 9:26
MemberMast Avalons6-Dec-11 9:26 
GeneralMy vote of 2 Pin
hfrmobile28-Jun-11 11:13
Memberhfrmobile28-Jun-11 11:13 
GeneralCompact Framework Pin
hfrmobile28-Jun-11 11:06
Memberhfrmobile28-Jun-11 11:06 
GeneralMy vote of 5 Pin
User97023-Apr-11 6:47
MemberUser97023-Apr-11 6:47 
GeneralIlmerge and WPF Pin
devvvy26-Jan-11 17:36
Memberdevvvy26-Jan-11 17:36 
AnswerRe: Ilmerge and WPF Pin
jmix9024-Feb-11 23:38
Memberjmix9024-Feb-11 23:38 
GeneralA point Pin
PIEBALDconsult12-Aug-10 4:30
professionalPIEBALDconsult12-Aug-10 4:30 
GeneralMy vote of 1 Pin
User 146370710-May-10 0:42
MemberUser 146370710-May-10 0:42 
GeneralFailed to run Pin
Tammam Koujan19-Jan-10 5:51
professionalTammam Koujan19-Jan-10 5:51 
GeneralRe: Failed to run Pin
hfrmobile28-Jun-11 11:12
Memberhfrmobile28-Jun-11 11:12 
GeneralILMerge GUI Pin
Lee.17-Oct-09 2:26
MemberLee.17-Oct-09 2:26 
GeneralRe: ILMerge GUI Pin
qualityking4-Sep-10 10:00
Memberqualityking4-Sep-10 10:00 
GeneralMerged DLL com registration Pin
William F8-Jun-09 6:17
MemberWilliam F8-Jun-09 6:17 
QuestionHow do you merge all the assemblies in the bin folder using ILMerge using command line Pin
azamsharp24-Jul-08 6:07
Memberazamsharp24-Jul-08 6:07 
GeneralWindows Mobile 6.0 Compatibility Pin
Mandeep Singh Sidhu23-Apr-08 2:31
MemberMandeep Singh Sidhu23-Apr-08 2:31 
GeneralRe: Windows Mobile 6.0 Compatibility Pin
hfrmobile28-Jun-11 11:16
Memberhfrmobile28-Jun-11 11:16 
GeneralCOM Pin
GAbirkan22-Dec-07 9:33
MemberGAbirkan22-Dec-07 9:33 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.