I made a simple exe program, configured Dotfuscator Professional Edition and started Build. Dotfuscator created a Dotfuscated folder containing a new exe file. I opened the new exe in DotPeek and there I can see exactly the same code as I wrote.
Earlier I also tried to use the free Dotfuscator Community version and got some kind of obfuscation.
What have I done wrong? Why does the free version work as expected while the professional does not?
DotPeek makes an effort to find the original source files on your computer when possible, using information contained in the debugging symbol files (.pdb files). This is especially noticeable if comments from the source show up in DotPeek, as the assembly (protected with Dotfuscator or not) never includes these comments.
Deleting these .pdb files should show the obfuscated code that's actually in the assembly.
(Note that I am a developer on the Dotfuscator team.)
eval_z). Try adding a comment to your source file, recompiling, re-running Dotfuscator, and checking if DotPeek shows you the comment. Also, your second image doesn't appear to be from the free Dotfuscator Community, as Control Flow obfuscation seems to be present. - Joe Sewellhttps://imgur.com/a/sILdKdS- Сергейexefile to other folder and rename it. after all manipulation dotPeek has shown obfuscation like this ::https://imgur.com/a/U13tdAH- СергейdotPeekopen other files. why ? - Сергей