Approximately Skater settings consent to generated names that choice prevent recompilation.
Public members in dll libraries are intentionally reserved as of obfuscation because they are calculated to be used in outer assembly code. Private and Public members names obfuscation scrambles names of classes, methods, variables, and new assembly members. If you are sure a little of public members are not to be accessed commencing outside, you may desire to obfuscate them.
For exe executables you may mull over the assemblies to be self-contained, and set obfuscation of all possible names vastly aggressively, counting Public Members.It makes assembly code reverse production much harder by obfuscating names.
Control Flow obfuscation anticipated to stop decompilers and deobfuscators on or after functioning correctly.
Control Flow obfuscation subdues reverse commerce by scrambling .NET methods (functions and procedures) code. The Control Flow obfuscation algorithm distorts and reorders the IL code in the assembly, inserting bait outlet instructions little preserving code semantics. Applying of this feature increases the bulk of the output assembly. This obfuscating effectively converts assembly structure implementations into "spaghetti code", manufacture interpretation by individual hackers and decompiler tools much extra difficult.
Actually Control Flow obfuscation involves the insertion of additional directives. If a maximum smooth of code protection is not necessary for your assembly, you may want to regard as disabling this feature to make light of your output executable code bulk.