Use cases
The situations people actually reach for this in — with the honest limits for each, so you can tell whether it fits yours.
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.
Free renaming raises the cost of reverse engineering. It does not make code unreadable on its own, and it will not stop a determined attacker. When renaming is not enough, Pro adds string encryption, control-flow obfuscation, reference proxying and method virtualization. Read what obfuscation actually protects against if you are deciding how much protection you need, which layers your project needs, or the comparisons.