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

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 MVP
http://simonrhart.blogspot.com


"jimhunt22@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

.

Relevant Pages

  • Re: Dotfuscator and ClickOnce
    ... I was able to apply a strong name to the application's executable by not doing it in Visual Studio ... but as part of the script I was using to run Dotfuscator. ... This occurs because obfuscation changes the binary by renaming all of the ... Authenticode signing of assemblies that you wish to obfuscate. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Problem using obfuscation
    ... I'm using Dotfuscator that comes along with the Visual studio.Net. ... I'm using obfuscation for the first time, so not sure how to use it ... obfuscate multiple assemblies which are using each other's public ... class libraries which use each other's classes too having refrence ...
    (microsoft.public.dotnet.security)
  • Re: Problem using obfuscation
    ... I'm using Dotfuscator that comes along with the Visual studio.Net. ... I'm using obfuscation for the first time, so not sure how to use it ... obfuscate multiple assemblies which are using each other's public ... class libraries which use each other's classes too having refrence ...
    (microsoft.public.dotnet.security)
  • RE: DotFuscator Prof- Project lost when changes made
    ... For some reason searching Managed Newsgroups for DotFuscator fails to find ... So to help people find it Obfuscator and Obfuscation and DotFuscator ... > Using a DotFuscator Professional v2.0 Project in Visual Studio 2003. ... > After creating and obfuscating a set of assemblies then closing visual studio ...
    (microsoft.public.vsnet.ide)
  • Re: Dotfuscator disassociates derived class when base class is lin
    ... any dependency assemblies the input assembly is dependent on. ... become disassocarted and calls to override functions in the base class ... obvioously this then defeats the purpose of obfuscation. ...
    (microsoft.public.dotnet.framework.compactframework)