microsoft
Report a problem

Microsoft ILMerge 2.0.7.1226

Slimy   on 27 December 2007 - 00:32 · 6 comments & 5088 views

Advertisement (Why?)
ILMerge is a utility that can be used to merge multiple .NET assemblies into a single assembly. ILMerge takes a set of input assemblies and merges them into one target assembly. The first assembly in the list of input assemblies is the primary assembly. When the primary assembly is an executable, then the target assembly is created as an executable with the same entry point as the primary assembly. Also, if the primary assembly has a strong name, and a .snk file is provided, then the target assembly is re-signed with the specified key so that it also has a strong name. ILMerge is packaged as a console application. But all of its functionality is also available programmatically. Note that Visual Studio 2005 does allow one to add an executable as a reference, so you can write a C# client that uses ILMerge as a library. If you are using Visual Studio 2003, you must use the v1.1 version of ILMerge and rename it to be a dll in order to use it as a reference.

There are several options that control the behavior of ILMerge. See the documentation that comes with the tool for details. The v2.0 version of ILMerge runs in the v2.0 .NET Runtime, but it is also able to merge v1 or v1.1 assemblies. However it can merge PDB files only for v2 assemblies. The v1.1 version of ILMerge can only process assemblies built in the v1.1 runtime (but does merge PDB files for those assemblies). Currently, ILMerge works only on Windows-based platforms. It does not yet support Rotor or Mono. It runs in the v2.0 .NET Runtime, but is also able to merge v1 or v1.1 assemblies.

System Requirements
Supported Operating Systems: Windows 2000; Windows Server 2003; Windows XP
Important: Make sure you have the latest service pack and critical updates for the version of Windows that you are running. To find recent security updates, visit Windows Update.

Download: Microsoft ILMerge 2.0.7.1226
Link: Home Page

Post a comment · Send to friend Comments · There are 6 additional comments
(5 replies) #1 bits on 27 Dec 2007 - 07:29
I believe this has something to do with assemblies
#1.1 Wivern on 27 Dec 2007 - 07:47
You think?
Quote -
ILMerge is a utility that can be used to merge multiple .NET assemblies into a single assembly.
#1.2 bits on 27 Dec 2007 - 08:13
Yes I in fact assembled that assembly belief all by my assembled self.

I think I'll donate a thesaurus to this teams marketing guy.
#1.3 FusionOpz on 27 Dec 2007 - 15:55
How about donating a brain to him while your at it.
#1.4 Skwerl on 27 Dec 2007 - 16:18
What, do you not understand what an assembly is or something? That's the only thing it can be called, since that's Microsoft's technical name for the entity.
#1.5 bits on 28 Dec 2007 - 07:07
Its not what it is, it is just a terrible way to get the point of it across.

First shalt thou take out the Holy Pin. Then shalt thou count to three, no more, no less. Three shall be the number thou shalt count, and the number of the counting shall be three. Four shalt thou not count, neither count thou two, excepting that thou then proceed to three. Five is right out. Once the number three, being the third number, be reached, then lobbest thou thy Holy Hand Grenade of Antioch towards thy foe, who, being naughty in my sight, shall snuff it.

Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

Advertisement (Why?)