When your assembly has been already strong name signed, it won't work after obfuscation, choose this option to remove the signature, so you can test out the obfuscated assembly. Our standalone desktop version re-signs the obfuscated code automatically.
CAUTION: When this option is choosed, the resulting assembly will not be able to re-signed afterwards, therefore, this option should be mainly used for testing purpose in the case you are not the author of the assembly and you do not have access to the key file. For more info, click here
delay sign
When your assembly has been already strong name signed, it won't work after obfuscation, choose this option so you can re-sign the obfuscated code afterwards. After you download the obfuscated assembly, you can do one of the following,
- invoke sn -Vr <assembly> to continue to work with the obfuscated assembly.
- invoke sn -R <assembly> <keyfile> to re-sign the obfuscated assembly when the key file is finally available.
For standalone applications (.exe files), you can select this option so our obfuscator will emit code to protect your assembly from being disassembled by the Microsoft ILDASM utility. When this option is chosen, ILDASM will crash when opening the obfuscated assembly, see the image below. Your assembly will be still able to execute on .NET platform.
This option will also protect against other utilities using reflection APIs, e.g., Reflector will not able to display and disassemble your .exe files after obfuscation.
By default, our obfuscator usually generates a smaller file. Sometimes, your assembly may not work after obfuscation, especially for mixed images that contain both managed and unmanaged code, you may then want to unselect this option, so your file size will not change.
By default, our obfuscator emits special pattern to protect against decompilation by our own salamander decompiler. Please select this option if you want to decompile your code with our decompiler.