need obfuscation

[Tina]

Is this Community Edition Obfuscator any good? Is there a good one or a
good method that doesn't cost so much money?
Thanks,
T

 

[Frans Bouma [C# MVP]]

Is this Community Edition Obfuscator any good? Is there a good one
or a good method that doesn't cost so much money? Thanks,
T

It's very good, though you have to help it.

One of the key things you have to do is to make as much classes and
methods PRIVATE or INTERNAL. This is essential. For example a .exe
project should have just all its classes internal and all methods
internal. This will give the obfuscator much more freedom to rename the
classes and methods.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

 

[Rad [Visual C# MVP]]

Is this Community Edition Obfuscator any good? Is there a good one or a
good method that doesn't cost so much money?
Thanks,
T

It's pretty good, but then again it depends on how much obfuscation you
want. For instance it doesn't encrypt strings. But all in all, pretty much
bang for the buck

 

[Chris Mullins [MVP]]

(As a humerous aside You could try using non normalized unicode strings as
in this approach:

http://blogs.msdn.com/michkap/archive/2005/02/07/368570.aspx

It sure made my head hurt just to look at! It's just... so wrong at every
level.

 

[Rad [Visual C# MVP]]

(As a humerous aside You could try using non normalized unicode strings as
in this approach:

http://blogs.msdn.com/michkap/archive/2005/02/07/368570.aspx

It sure made my head hurt just to look at! It's just... so wrong at every
level.

Oh my goodness!! That's verging on the illegal!!!

 

[RobinS]

That looks cool! I stared at it for at least a second before I realized all
the a's were different.

Robin S.
------------------------

(As a humerous aside You could try using non normalized unicode strings
as in this approach:

http://blogs.msdn.com/michkap/archive/2005/02/07/368570.aspx

It sure made my head hurt just to look at! It's just... so wrong at every
level.