ILSpy CLI tips — authorized .NET decompile checklist
For legal, authorized and educational use only. Only analyze software you own or have written permission to examine.
Quick answer
ILSpy / ilspycmd tips keep authorized .NET decompiles reviewable. Start from ilspy-overview-authorized.
On this page
Snapshot
| Field | Value |
|---|---|
| Surface | ILSpy CLI tip checklist |
| Job | Authorized .NET decompile / export hygiene |
| Sibling | ILSpy overview |
| Peer | dnSpyEx vs ILSpy |
Tip checklist (authorized only)
- Confirm the assembly is one you own or are authorized to decompile; hash before run.
- Record ILSpy / ilspycmd / decompiler library versions in Evidence.
- Prefer an explicit output directory under case control.
- Quote the exact CLI (or GUI export path) you used; document failures honestly.
- Keep originals hashed; treat decompiled projects as derived Evidence.
- Escalate debugger-style needs to authorized dnSpyEx pages — do not invent a debugger ILSpy never was.
Allowed framing
- Classroom decompiles of student-built .NET assemblies and courseware.
- Teaching batch export literacy with logged commands.
- Comparing ILSpy vs dnSpyEx as tooling choices under one case ID.
- Saving decompiled trees hashed beside the case assembly.
Scope we will not cover
- No crack/keygen / DRM-bypass for commercial .NET apps.
- No malware packaging or dropper rebuild cookbooks.
- No unauthorized decompile of third-party production assemblies for redistribution.
- No credential-theft how-tos framed as "string hunting."
Beginner path (authorized only)
- Read ilspy-overview-authorized.
- Hash one authorized assembly; run one syllabus-approved CLI/export step.
- Save output path + version strings as Evidence.
- Optional: compare product fit via dnSpyEx vs ILSpy.
- Stop at literacy — no crack framing.
Which to pick
- Prefer authorized assemblies, hashed originals, and logged CLI/exports.
- Use the overview for orientation; this page for CLI checklist practice.
- No crack or malware packaging framing.
For legal, authorized and educational use only.
FAQ
How is this different from ilspy-overview-authorized?
ILSpy overview is orientation. This page is a short CLI / automation tip checklist — it does not overwrite that overview.
ILSpy GUI vs CLI (ilspycmd)?
GUI for interactive exploration; CLI for batch/courseware pipelines and logged Evidence. Prefer the surface your syllabus names.
ILSpy vs dnSpyEx?
See dnSpyEx vs ILSpy. Keep labels honest — different products, overlapping jobs.
Can ILSpy CLI crack .NET licenses?
No. BinBench will not publish crack/keygen or DRM-bypass cookbooks.
Does this teach malware packaging for .NET?
No. Authorized assembly literacy only — no malware packaging cookbooks.