ILMerge
ILMerge is a static linker for .NET Assemblies. (by dotnet)
dnlib
Reads and writes .NET assemblies and modules (by 0xd4d)
| ILMerge | dnlib | |
|---|---|---|
| 7 | 1 | |
| 903 | 2,056 | |
| - | 1.7% | |
| 1.0 | 7.2 | |
| almost 4 years ago | 9 days ago | |
| C# | C# | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ILMerge
Posts with mentions or reviews of ILMerge.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-09.
-
Could compiled code in dynamically linked libraries be statically baked into an executable?
You can do this with .NET: https://github.com/dotnet/ILMerge
-
How to build my console app as single .exe file?
Cause it's possible since .NET Core 3.0. For legacy projects i suggest use ILMerge static linker.
-
Amateur needing suggestions on the best environment / tool for this project
Are you sure all those files are necessary for running the .EXE? Perhaps after a compile, try copying just the .EXE from the release folder to somewhere else on your machine. You may find it runs just fine. If not, perhaps look at something like ILMerge for packaging it into a single .EXE
-
Assembly.Load alternative?
Combine applications by merging IL, not by storing it in resources. (il-merge, il-repack and unknown to me 'libz', or write your own merger using Mono.Cecil or dnLib)
-
Is there any internal command line parser in dotnet
Depending on which version of .NET you're building with, there are various tools to allow you to statically link all of your assemblies into one executable. Examples are ILMerge for .NET Framework and ILRepack for .NET Core.
-
Combining DLLs into one? Or embed as resource? VB.net
You can try ILMerge, which allows merging multiple assemblies into one.
-
Plug-in script - how to avoid assembly versioning mismatch?
I've had relatively good success using ILMerge to merge assemblies together to avoid these types of issues. I've had one project that had issues (the most complex one I worked on), but all the smaller ones have worked just fine. Just download it from NuGet, plus one of the NuGet packages that combine it into the build process (ILMerge.MSBuild.Task or MSBuild.ILMerge.Task) and it'll automatically merge your end result as part of the build process.
dnlib
Posts with mentions or reviews of dnlib.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-14.
-
Assembly.Load alternative?
Combine applications by merging IL, not by storing it in resources. (il-merge, il-repack and unknown to me 'libz', or write your own merger using Mono.Cecil or dnLib)
What are some alternatives?
When comparing ILMerge and dnlib you can also consider the following projects:
ILRepack - Open-source alternative to ILMerge
LibZ - LibZ, the alternative to ILMerge
command-line-api - Command line parsing, invocation, and rendering of terminal output.
Costura - Embed references as resources