|
I have been toying with Xenocode and I am with you on the fact that it breaks the EXE. I turned off any ANTI-ILDASM so reflection would work correctly and basically turned every option off or way down like control flow obfuscation and it did finally make a working exe. I could never get the .NET runtime to link with the assembly so that I wouldn't have to make users download it if they didn't want to. If I ran my app it would come up with a debugger error and ask me which development tool to open it up in. I can't even get the merge multiple modules to work correctly. I am tinkering with Microsoft's ILMERGE utility as they keep updating it every few months now.
9Rays.NET Spices obfuscator has a 199.00 console version which he says has the identical obfuscation features of their GUI and VSIP edition. They protect their own tools with it they say so it may be worth trying as it has a good bit of features that Dotfuscator doesn't and the demo version didn't break my EXE lol.
Now you have me wondering if they improved the Dotfuscator community edition for VS.NET 2005 ? I have it installed on another partition for testing and I imagine they updated it to handle the .NET 2.0 framework but I assume it still has the same limitations as the older one (No string encryption, flow control, etc...)
|