danhaa.blogg.se

The download site and this common Nuget tutorial show how it works. fully unreadable.Įazfuscator.Net: Installable via Nuget Package Manager for Visual Studio. “c:path_to_confuser ” “$(SolutionDir)confuserSettings.crproj”Įcho “not in release mode, not obfuscating” it does not make much sense to obfuscate your code with the Dotfuscator Community Edition.Īfter testing some other free obfuscation tools, I can recommend these ones:Ĭonfuser: You can configure your settings via GUI, save them and execute them via command-line (and also via Visual Studio Post Build event): Testing the obfuscated files with this free Obfuscation Checker, you will see the generated Dotfuscator code has very few differences to the original code, i.e. You can also use the code below, the code is only obfuscated when running Release mode.Ĭd “$(ProjectDir)$(IntermediateOutputPath)”įor /f “tokens=*” %%a in (‘dir /b *.exe *.dll’) do “C:Program Files (x86)Microsoft Visual Studio 10.0PreEmptive SolutionsDotfuscator Community EditiondotfuscatorCLI.exe” /in:%%a Otherwise you will have problems with debugging your application in the future. The same tutorial should work for Visual Studio 2012 too.ĭelete the post build code after processing. Then build your project and you get your obfuscated solution as Setup file. “C:Program Files (x86)Microsoft Visual Studio 10.0PreEmptive SolutionsDotfuscator Community EditiondotfuscatorCLI.exe” /in:$(TargetFileName)Ĭopy /y “$(TargetDir)Dotfuscated$(TargetFileName)” “$(TargetDir)$(TargetFileName)”