dotnet/ILMerge
ILMerge is a static linker for .NET Assemblies. observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3646
- days_rel: n/a
- days_push: 2246
- n_releases_24m: 0
Adoption not part of the score
1306 stars · 179 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
ILMerge is a static linker that merges multiple .NET assemblies into a single assembly, available as a console application and a NuGet package with MSBuild integration. It preserves entry points and can re-sign merged assemblies with strong names.
Use cases
- merge multiple .NET dlls into one executable
- bundle .NET assemblies into a single file for distribution
- combine c# project dependencies into one assembly
- statically link .net libraries into my app
- re-sign merged assembly with strong name key
- integrate assembly merging into msbuild build
When to choose
- you need to ship a .NET Framework app as a single file on Windows
- you want MSBuild/NuGet integration for assembly merging
- you need strong-name re-signing of merged assemblies
When to avoid
- you target .NET Core/.NET 5+ (prefer single-file publish or ILRepack alternatives)
- you need cross-platform merging on Linux or macOS
- you need Mono support
Facets
cli-tool · maturity maintenance
build-tool cli developer-tools developer-tools compilers windows dotnet cli assembly-merging static-linker il-merging nuget-package msbuild-integration strong-naming dotnet
1 source
- readme: https://github.com/dotnet/ILMerge · fetched 2026-08-28 · 493fc80a879b
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| dotnet/ILMerge | main | 10 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem