Howdy folks -
I have been using DotFuscator Community Edition to try to obfuscate my code-behind code that is compiled into a .DLL. I've been able to use DotFuscator on the DLL without a problem and it makes a perfectly nice obfuscated DLL assembly after building.
The problem arises when you want to use this with ASP.NET. Since the functions/objects are renamed, the .ASPX web pages can't find the code-behind and raise errors, such as:
* Parser Error Message: Could not load type 'XXX.content'. (where XXX is the name of the project and content refers to content.aspx).
So, then I check "content" to be left out of the renaming process and it raises an error about a dropdown population function on the page:
* Compiler Error Message: CS0117: 'ASP.content_aspx' does not contain a definition for 'selProduct_Changed'
I scoured the web, finding some notes that publicly-accessible classes and functions need to be left out of the renaming process for them to work. However, it seems that you need to completely disable "Renaming" in order for a DotFuscated DLL to work at all with ASP.NET.
Questions:
1. Is there a way to make DotFuscator work with ASP.NET in a way that obfuscates the DLL such that all of the functions and objects are renamed?
2. Is DotFuscator doing anything useful even with "Renaming" disabled? A simple use of Lutz's Reflector lets me see all sorts of things in the DLL, leading me to believe that my code could be easily reverse engineered.
Any expert opinions would be much appreciated by this aspiring code obfuscator.
------------------------
Do androids dream of electric sheep?