Re: Dotfuscator disassociates derived class when base class is lin

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

For CF, check out this, it is a very good tool:
http://fabdecret.blogspot.com/2007/09/obfuscator-for-compact-framework.html

BR

Fabien Decret (Device Application Development MVP)
Windows Embedded Consultant

ADENEO (ADESET)
http://www.adeneo.adetelgroup.com/ | http://fabdecret.blogspot.com/


On 3 fév, 14:13, Simon Hart [MVP] <srhart...@xxxxxxxxx> wrote:
I tried Dotfuscator in the early days I think way back in .NET 1.1 and could
never get it to behave and I think many other developers have found the same
problem that I have come across. There are better obfuscator tools out there
but you will have to pay for them.

See here:http://www.howtoselectguides.com/dotnet/obfuscators/

I'm just gussing but that rename referenced metadata option would obfuscate
any dependency assemblies the input assembly is dependent on.
--
Simon Hart
Visual Developer - Device Application Development MVPhttp://simonrhart.blogspot.com



"jimhun...@xxxxxxxxxxxxxx" wrote:
On 1 Feb, 09:53, jimhun...@xxxxxxxxxxxxxx wrote:
I've run into an odd problem using the Dotfuscator tool.  I have a
reasonably large PDA C# Winfoms application that when obfuscated "as-
is" works fine on the device.  However, when I "link" together a
number of assemblies then the application becomes broken.  One of the
assemblies in the Linking is a base class of a number of other
assemblies. When it's linked in the inheritance hierachy appears to
become disassocarted and calls to override functions in the base class
(which previously successfully called the derived class before
linking) now fail to call the override functions in the derived
class.  It's like as far as the base class is concerned the derived
class does not exist anymore.  I found that if I exclude the base
class function from obfuscation then it all works correctly again -
obvioously this then defeats the purpose of obfuscation.

I would like to understand why this is happeneing - I believe it to be
a bug in the Dotfuscator tool, but I am open to suggestions

Jim

Hmmm, it seems the problem is being caused by checking the "Rename
referenced metadata defined only in input file" option on the "Rename-
Options" tab.  Anyone have any idea what this does - there is nothing
on Google and nothing in the Dotfuscator that explains its meaning.
What is the effect of unchecking this?

Jim- Masquer le texte des messages précédents -

- Afficher le texte des messages précédents -

.

Relevant Pages