After obfuscating, when I decompile the dll’s from the reflector I can see all the method names of my abstract classes.Body of My method are also easily Understandable.
All my classes names are also seen e.t.c
Can By any technique I can make my class not understandable or these can’t be open in Reflector?

“So if you want to disable renaming of your class you may write something like an example below (C#):

Example 4.1. Disabling class renaming

[System.Reflection.ObfuscationAttribute(Feature = “renaming”, ApplyToMembers = false)]
class MyOneThousandAndFirstClass
{
…
}

If you want to disable renaming of your class and all its members you may write:

Example 4.2. Disabling class and its members renaming

[System.Reflection.ObfuscationAttribute(Feature = “renaming”, ApplyToMembers = true)]
class MyOneThousandAndSecondClass
{
…
}

If you want to disable renaming of the properties in your class you may write:

Example 4.3. Disabling class properties renaming

[System.Reflection.ObfuscationAttribute(Feature = “properties renaming”)]
class MyOneThousandAndThirdClass
{
…
}”

Now I can only say: HOLY CRAP!

It can compete with all the best obfuscators out there and it’s free. I L O V E Y O U!

“YOU JUST KILLED ALLexceptionsname should not be obfuscated or changed.”

should have been:

“YOU JUST KILLED ALL OBFUSCATORS, EVEN THE EXPENSIVE ONES! I have just one request, pleeeease, if you can, implement a way to specify methods that SHOULDN’T be renamed at all. For instance, if you make a .dll for others to use, they must be able to call something like “SomeThing.DoSomething()”, and therefore there’s a need to be able to specify that “do not rename SomeThing.DoSomething()”. Other than that pet peeve (and it is quite a big feature so please see if you can do it), you’ve created a WINNER!”

Thank you SO MUCH for creating Eazobfuscator! I LOVE YOU!

You support just about EVERYTHING that even the most PROFESSIONAL, thousand-dollar obfuscators do!

- String encryption!
- Method signatures overload induction(THIS BLOWS MY MIND!!! the single BEST FEATURE of ANY obfuscator and you provide it for FREE!!!)
- Assemblies merging!!
- Supports .NET Compact Framework versions 2.0 and 3.5!!
- Microsoft Visual Studio integration!!
- Supports automatic builds!!

YOU JUST KILLED >ALLexceptionsname< should not be obfuscated or changed.

Other than that pet peeve (and it is quite a big feature so please see if you can do it), you’ve created a WINNER! I can HARDLY believe that you actually support METHOD OVERLOADING! The single, strongest protection that you can give a .NET assembly (for anyone reading who doesn’t know what that is, it means that it renames ALL/most methods to the same name, such as ‘A’. the runtime still knows what method to use based on the number/type of arguments, but a human can hardl yread it since it’s a bunch of A(…) calls on every line.)

The closest to a good freeware obfuscator was Skater .NET, it supports loads of features except method overloading.

So you just KILLED IT!

Thanks again, you are awesome!

I’ve been searching for a free .NET obfuscator for a while, and this tool seems to be the best choice currently available.

There is a google group dedicated to Eazfuscator.NET available. If have a suggestion or bug report then you can send and discuss it at http://groups.google.com/group/eazfuscator-net .

I have no plans to support SharpDevelop yet. But if it’s easy to implement then it may appear in version 2.0 of Eazfuscator.NET.

Regards

Does your obfuscator work with SharpDevelop or will you have a version planned to support this environment?

We have planned server power offs during April weekends because of electric network reconstruction performed by electrical company.

Regards

So, where can I download your obfuscator from?

Thanks in advance for your reply.