ILMerge Properties

Command line option: [/allowDup[:typeName]]*

Default: no duplicates of public types allowed.

Command line option: /allowMultiple

Default: false

This can be used to allow C++ assemblies to be merged; it does not appear that the C++ compiler writes the value as ILonly.

However, if such an assembly has any non-IL features, then they will probably not be copied over into the target assembly correctly.

So please use this option with caution.

Command line option: /zeroPeKind

Default: false

It will also be used to get the Win32 Resources from. It is mutually exclusive with the CopyAttributes property (Section 2.7).

When it is not specified, then the Win32 Resources from the primary assembly are copied over into the target assembly.

If it is not a full path, then the current directory is used.

Command line option: /attr:filename

Default: null

An assembly is considered part of the transitive closure if it is referenced, either directly or indirectly, from one of the originally

specified input assemblies and it has an external reference to one of the input assemblies, or one of the assemblies that has such a reference.

Command line option: /closed

Default: false

Any duplicate attribute overwrites a previously copied attribute. If you want to allow duplicates (for those attributes whose type specifies “AllowMultiple” in their definition), then you can also set the AllowMultipleAssemblyLevelAttributes.

The input assemblies are processed in the order they are specified. This option is mutually exclusive with specifying an attribute assembly, i.e., the property AttributeFile.

When an attribute assembly is specified, then no assembly-level attributes are copied over from the input assemblies

Command line option: /copyattrs

Default: false

If you do not want a .pdb file created for the output assembly, either set this property to false or else specify the /ndebug option at the command line.

Command line option: /ndebug

Default: true

Command line option: /delaysign

Default: null

the path and filename that will be used to identify types that are not to have their visibility modified.

If Internalize is true, but ExcludeFile is "", then all types in any assembly other than the primary assembly are made non-public.

Setting this property implicitly sets Internalize to true. The contents of the file should be one regular expression per line.

The syntax is that defined in the .NET namespace System.Text.RegularExpressions for regular expressions.

The regular expressions are matched against each type's full name, e.g., "System.Collections.IList".

If the match fails, it is tried again with the assembly name (surrounded by square brackets) prepended to the type name.

Thus, the pattern “\[A\].*” excludes all types in assembly A from being made non-public. (The backslashes are required because the string is treated as a regular expression.)

The pattern “N.T” will match all types named T in the namespace named N no matter what assembly they are defined in.

It is important to note that the regular expressions are not anchored to the beginning of the string; if this is desired, use the appropriate regular expression operator characters to do so.

Command line option: /internalize[:excludeFile]

Default: null

Command line option: /align:n

Default: 512

have their visibility modified so that they are not visible from outside of the merged assembly. A type is exempt if its full name matches a line from the ExcludeFile (Section 2.10) using the .NET regular expression engine.

Command line option: /internalize[:excludeFile]

Default: false

then have a strong name. It can be used with the DelaySign property (Section 2.9) to have the target assembly delay signed.

This can be done even if the primary assembly was fully signed.

Command line option: /keyfile:filename

Default: null

Command line option: /log[:logfile]

Default: null

If Log is true, but LogFile is null, then log messages are written to Console.Out. To specify this behavior on the command line, the option "/log" can be given without a log file.

Command line option: /log[:logfile]

Default: false

Command line option: /out:filename

Default: null

Command line option: /out:filename

Default: true

Command line option: /lib:directory

This can occur when an .snk file is not specified, or if something goes wrong trying to read its contents.

assembly will be the same kind as that of the primary assembly. (In that case, the file extensions found on the specified target assembly and the primary

assembly must match.) When it is specified, then the file extension of the target assembly must match the specification. The possible values are ILMerge.Kind.{Dll, Exe, WinExe}

Command line option: /target:(library|exe|winexe)

Default: ILMerge.Kind.SameAsPrimaryAssembly

The "v" is case insensitive and is also optional. This way ILMerge can be used to "cross-compile", i.e., it can run in one version of the framework and generate

the target assembly so it will run under a different assembly. The second argument is the directory in which mscorlib.dll is to be found.

Command line option: /targetplatform:version,platformdirectory

Default: null

The "v" is case insensitive and is also optional. This way ILMerge can be used to "cross-compile", i.e., it can run in one version of the framework and generate

the target assembly so it will run under a different assembly. The second argument is the directory in which mscorlib.dll is to be found.

Command line option: /targetplatform:version,platformdirectory

Default: null

types in the input assemblies: it contains all of the members from each of the corresponding types in the input assemblies. It cannot be specified at the same time as /allowDup.

Command line option: /union

Default: false

version is read in as a string and should look like "6.2.1.3" (but without the quote marks). The version must be a valid assembly version as defined by the attribute AssemblyVersion in the System.Reflection namespace.

Command line option: /ver:version

Default: null

Command line option: /xmldocs

Default: false