ILSpy helps inspect managed .NET assemblies, their types, methods and decompiled code. It suits questions about a .NET application's call chain or public API before a runtime test is necessary. Keep the exact assembly version and check whether native dependencies or generated code affect the path. Readable output still differs from the original developer source.
First investigation
Start with assembly metadata and type names, then follow a bounded call chain. Mark renamed or inferred behavior as a hypothesis until it can be connected to CIL or a controlled run.
Limits
Obfuscation and compiler choices can erase meaningful names or alter apparent structure. ILSpy describes the managed portion of a program; native modules and external services require separate evidence.
Requirements & evidence
- Resource type
- Tool
- Category
- .NET
- Host platforms
- Windows, Linux, macOS
- Targets
- dotnet
- Level
- Unknown
- Price / availability
- Unknown
- License
- MIT
- Interface
- GUI and CLI
- Input formats
- Unknown
- Architectures
- Unknown
- REA integration
- Unknown
- MCP support
- Unknown
- Maintenance
- Unknown
- Repository activity
- 2026-11-04T08:51:02Z
- Archived
- No
- Source checked
- 2026-11-04T10:07:14.283497+00:00
Latest observed repository release: v11.2. Latest GitHub release in this repository; may belong to one component, not the entire product.
Repository: Official repository
Primary sources
- https://api.github.com/repos/icsharpcode/ILSpy
- https://raw.githubusercontent.com/icsharpcode/ilspy/master/README.md
- https://raw.githubusercontent.com/icsharpcode/ilspy/master/LICENSE
Source descriptions establish documented scope. They do not establish that every workflow has been reproduced by AI Craft Pad.