Skip to content

Reference

FAQ

Common questions about Glass.NET — licensing, platforms, the decompiler engine and how it compares to ILSpy, dnSpy and .NET Reflector.

Is Glass.NET really free?

Yes — completely free, no account, no seats, no limits. It’s our contribution to the .NET community.

Is it OK to decompile an assembly?

Glass.NET is a developer tool for legitimate work: inspecting and debugging your own binaries, understanding a dependency you rely on, checking what an obfuscator produced, interoperability, security review, and recovering your own lost source. Use it only on software you have the right to analyze, and respect the license terms and intellectual-property rights of others. Don’t use Glass.NET to infringe copyright, circumvent licensing, or misappropriate someone else’s code.

What engine does it use?

Glass.NET is built on ICSharpCode.Decompiler, the same proven engine behind ILSpy. Glass adds a fast navigation model (Go to Definition, Find All References, Go To All, call/type hierarchy, history and breadcrumbs), C#/IL views and project export on top.

How does it compare to ILSpy, dnSpy or .NET Reflector?

Glass focuses on navigation: Go to Definition, Find All References, Go To All, call/type hierarchy, history and breadcrumbs, plus C#/IL views and project export. It’s free (unlike .NET Reflector) and built to make reading unfamiliar assemblies fast.

Does it run the assemblies it opens?

No. Glass performs static analysis only — it reads metadata and IL and reconstructs C#. It never executes the target assembly.

What can it open?

Managed .NET assemblies (.dll / .exe) targeting .NET Framework and .NET 6–10. Native (non-managed) binaries are rejected with a clear message.

Which platforms are supported?

The current release is a self-contained Windows build. The app is built on Avalonia, so cross-platform builds are on the roadmap.

Where do I report a bug or request a feature?

Open an issue on the Glass.NET releases repository or contact us.