.NET code Protection
Assemblies are obfuscated, then method bodies are replaced by corruped code;
decompilation and disassembly tools like ILDASM can no more unassemble methods.
Components Protection
dotNet Protector 5 builds a new .Net assembly. This new feature enables not
only exe protection, but dll as well. ASP.Net is supported by dotNet Protector
5.
Evaluation Generator
dotNet Protector can generate a limited executable. You can choose executable
lifetime (in days): your program wont launch beyond this limit. You also choose
to limit execution time in minutes.
No modification to your code is necessary to produce an evaluation version.
Activate your software
A hardware lock system is integrated with dotNet Protector. Running your
program can depend on a valid unlock key. Configuration collection and
activation code generation are embedded features of dotNet Protector.
Configuration comparison and unlock key generation functions are built in
dotNet Protector.
Keys used for activation are UNIQUE: a new Key set is generated during install.
This set, composed of public and private keys will allow you to unlock only
your applications, and THIS SET ONLY will be able to unlock them. Your
application embed the public part of your set; the protected part is use to
generate your application and unlock it you keep it secret. This way you keep
control of the whole activation process.
Script usage
dotNet Protector is a command-line application; without parameters, it works in
interactive mode. You can protect your code immediately after compilation by
adding an after generation event in your visual studio project; then protection
is automatically performed after compilation.