.NET applications are easier to inspect than many teams expect. Since .NET applications compile to Microsoft Intermediate Language (MSIL), decompilers can often convert compiled assemblies back into readable code.
This can expose sensitive parts of your application, including:
- Licensing logic
- Copy protection mechanisms
- Proprietary business logic
- Security-sensitive implementation details
- Intellectual property that gives your product its value
Dotfuscator helps reduce this risk by applying protection after your application is compiled.
Dotfuscator Protection
Dotfuscator protects compiled .NET assemblies by making them harder to understand, reverse engineer, modify, or reuse.
Obfuscation changes the structure and readability of compiled code while preserving the application’s intended behavior. For example, Dotfuscator can rename symbols, transform control flow, and apply other protection techniques that make decompiled output more difficult to interpret.
Dotfuscator can also add runtime Checks that detect suspicious conditions, such as:
- Debugging
- Tampering
- Running on rooted Android devices
These protections help make your application more resistant to inspection and unauthorized modification.
Post-Compile Protection
Dotfuscator is a post-compile tool. It protects the .NET assemblies, such as .dll and .exe files, that your build process creates. Dotfuscator does not require you to change your source code or development environment to start protecting your application.
A typical build process with and without Dotfuscator looks as follows:
The protected assemblies run on the Common Language Runtime (CLR) like standard assemblies, unless you intentionally configure protection settings that change runtime behavior.
When to Use Dotfuscator
Use Dotfuscator when you want to help protect .NET applications before release, especially if your application includes:
- Commercial or enterprise logic
- Licensing or entitlement checks
- Sensitive workflows
- Mobile or desktop code that users can access locally
- Intellectual property that should be harder to inspect or reuse
Dotfuscator does not replace secure coding practices, access controls, or server-side validation. Instead, it adds another layer of protection for compiled application code.
Next Steps
To begin using Dotfuscator Professional:
- Review Supported Frameworks and Development Tools.
- Review the System Requirements.
- Install Dotfuscator Professional.
- Review the Activation process.