Use cases

The situations people actually reach for this in — with the honest limits for each, so you can tell whether it fits yours.

ISVs and independent developers Commercial desktop applications Your WPF or WinForms app ships to customers' machines — and so does its source, effectively. Read more → Component vendors and NuGet publishers Paid libraries and SDKs You sell code to other developers, so your public API must stay intact while the implementation behind it does not. Read more → Anyone selling software with an activation step Licensing and trial enforcement The honest version: obfuscation makes licence code harder to find, not impossible to defeat. Read more → ISVs shipping server software into client environments On-premise and customer-hosted software Your server product runs on infrastructure your customer's administrators fully control. Read more → Teams delivering custom software to clients Agencies and consultancies You hand over a build, not your source — obfuscation keeps that boundary meaningful. Read more →

The common thread

Every case here comes down to the same fact: a .NET assembly carries the metadata needed to reconstruct readable C#, and once you ship a build, whoever holds it can read it. Renaming that metadata is what this tool does.

It raises the cost of reverse engineering. It does not make code unreadable, it does not encrypt strings, and it will not stop a determined attacker — see what obfuscation actually protects against if you are deciding how much protection you need, or the comparisons if you need more than renaming.