ILMerge 2.14.1208
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.
There are several options that control the behavior of ILMerge. See the documentation that comes with the tool for details.
Showing the top 20 packages that depend on ILMerge.
| Packages | Downloads |
|---|---|
|
MSBuild.ILMerge.Task
MSBuild ILMerge task allows you to use the famous ILMerge utility (ILMerge nuget package, see http://research.microsoft.com/en-us/people/mbarnett/ILMerge.aspx) in automated builds and/or Visual Studio 2012 projects.
It is similar to the ILMerge.MSBuild.Tasks nuget package, originally published by neoeinstein@gmail.com (that seems to be abandoned) with the following additional features:
- It supports all the latest ILMerge options;
- ILMerge.exe is discovered as package dependency;
- The .targets file overrides the CopyFilesToOutputDirectory build target, leaving the AfterBuild target free for further customizaton;
- It attempts to guess the reasonable merge order for the included assemblies and lets you to finetune it with a configuration file.
ILMerge.exe is not included into this package because its license prohibits redistribution. Referencing it as package dependency and loading it from its package location ensures that the latest ILMerge version is always used.
|
33 |
|
MSBuild.ILMerge.Task
MSBuild ILMerge task allows you to use the famous ILMerge utility (ILMerge nuget package, see http://research.microsoft.com/en-us/people/mbarnett/ILMerge.aspx) in automated builds and/or Visual Studio 2013/15 projects.
It is similar to the ILMerge.MSBuild.Tasks nuget package, originally published by neoeinstein@gmail.com (that seems to be abandoned) with the following additional features:
- It supports all the latest ILMerge options;
- ILMerge.exe is discovered as package dependency;
- The .targets file overrides the CopyFilesToOutputDirectory build target, leaving the AfterBuild target free for further customizaton;
- It attempts to guess the reasonable merge order for the included assemblies and lets you to finetune it with a configuration file.
ILMerge.exe is not included into this package because its license prohibits redistribution. Referencing it as package dependency and loading it from its package location ensures that the latest ILMerge version is always used.
MS Dynamics CRM users: merging in Microsoft.Xrm.Sdk may crash your plugin, exclude it from the merge with Copy Local=false.
|
4 |
|
MSBuild.ILMerge.Task
MSBuild ILMerge task allows you to use the famous ILMerge utility (ILMerge nuget package, see http://research.microsoft.com/en-us/people/mbarnett/ILMerge.aspx) in automated builds and/or Visual Studio 2019 projects.
It is similar to the ILMerge.MSBuild.Tasks nuget package, originally published by neoeinstein@gmail.com (that seems to be abandoned) with the following additional features:
- version 2.0 is able to merge packages referenced from SDK-style projects;
- It supports all the latest ILMerge options;
- ILMerge.exe is discovered as package dependency;
- The .targets file overrides the CopyFilesToOutputDirectory build target, leaving the AfterBuild target free for further customization;
- It attempts to guess the reasonable merge order for the included assemblies and lets you to fine-tune it with a configuration file.
ILMerge.exe is not included into this package because its license prohibits redistribution. Referencing it as package dependency and loading it from its package location ensures that the latest ILMerge version is always used.
NB: to use non-default configuration, copy ILMerge.props from package content folder to your project and add <Import Project="ILMerge.props" /> to the .csproj file.
|
1 |
This package has no dependencies.