If there's good obfuscation routines, it occurs to me there's deobfuscators, aka pretty printers. No, I've not tried it, just a thought. Obviously variable and function names don't get fixed.
Mike On Tue, Sep 29, 2020, 08:59 Preet Sangha <preetsan...@gmail.com> wrote: > I think you can use the command line for this. I don't use it but a quick > google gave me : > https://www.preemptive.com/dotfuscator/pro/userguide/en/interfaces_command_line.html > > regards, > Preet, in Auckland NZ > > > > On Tue, 29 Sep 2020 at 11:24, Greg Keogh <gfke...@gmail.com> wrote: > >> Folks, for the first time I have to obfuscate some assemblies that >> contain proprietary algorithms. I'm playing with the built-in Community >> edition. I'm disappointed to find that it's not integrated into Visual >> Studio in any way I can find, I have to use a separate app to create an XML >> file for each 'fuscate. Then how do I add that into my local build >> pipeline, post build commands or PS scripts? And my libraries are >> multi-platform targeted, so I have to process them all? Then I want to >> build NuGet packages, and so on. My first impression is that adding >> dotfuscator is like a spanner thrown into my nice simple local build and >> deploy process. >> >> Before I start reinventing wheels everywhere I thought I'd ask in here >> first if anyone has been down this road and has some suggestions. >> >> *Greg K* >> >
