Learn
Practical guides on protecting .NET assemblies — how obfuscation works, what it genuinely defends against, and how to fit it into a real build pipeline.
Guides
Guide
How to obfuscate a .NET DLL or EXE
A step-by-step walkthrough of obfuscating a compiled .NET assembly, what changes in the output, and how to verify the result still runs.
Guide
Obfuscating .NET builds in CI/CD
Wire the obfuscation API into GitHub Actions, Azure Pipelines or a local build script so every release artifact is protected automatically.
Guide
Obfuscation and reflection: what breaks and why
Renaming is safe until something looks up a member by name. Serialization, DI containers and XAML are the usual suspects — here is how to avoid each trap.
How it works
Concept
What .NET obfuscation actually protects against
Obfuscation raises the cost of reverse engineering — it is not encryption. Here is an honest breakdown of the threats it addresses and the ones it does not.
Concept
How .NET decompilers read your code
ILSpy, dnSpy and dotPeek can reconstruct near-original C# from a shipped assembly. Understanding why explains exactly what obfuscation changes.
Concept
Why public names are only renamed for EXEs
A library's public surface is its contract with callers. This explains the rule, when to enable public renaming, and how to ship a protected library safely.