Home - Forums-.NET - Spices.Net - Bad named class with "a" before the real name

Spices.Net

NET code security, tools to protect, obfuscate, tamper defense, code and data safety, recover, convert, optimize, explore, browse and analyze .Net software.

This forum related to following products: Spices.Net Suite, Spices.Net Obfuscator, Spices.Net Decompiler

Bad named class with "a" before the real name
Link Posted: 29-May-2009 00:32
When i perform a Spice.net obfuscation I found one class (only one) bad named.
That public class whose name was "Azienda" become "aAzienda". I tried with excludes option without success.
I'm using 9Rays.Spices.Net Ver. 5.13.5, runtime version v2.0.50727. My solution is developed with VS2005 and VB.NET.

Could you help me?

Thanks
Link Posted: 29-May-2009 00:45
There are a few ways to solve that problem:
1. Please mark this class with NotObfuscate attribute
2. Or add to the ExclusionPatterns collection of your spices.project fullname of your class (with namespace: MyCompany.MyClass).
Also I'd recommend you to upgrade your version of Spices.Net to the latest version v5.6.2.
Link Posted: 29-May-2009 01:14
Thank you.
I tried with the ExclusionPatterns collection with namespace: MyCompany.MyClass* without success.

Could you give me the correct link to download the latest realease?

I'm getting crazy! Yesterday it was good, today no!

Best regards.
Link Posted: 29-May-2009 01:23
I tried with the ExclusionPatterns collection with namespace: MyCompany.MyClass* without success.


Try just MyCompany.MyClass string. Also make sure that this is a full name of class

Could you give me the correct link to download the latest realease?


You should visit our site, log on and visit Downloads section to find marked by green color available for downloading product. If you can't find link available for downloading probably your annual subscription is expired. In that case you can renew your subscription to the next year for the half of regular price.

I'm getting crazy! Yesterday it was good, today no!

Oh, don't worry, that's solvable problem. You can send us your spices.project and original assembly to solve that problem as soon as possible.
Link Posted: 29-May-2009 03:35
I found the solution!!

Sometime I use an istance name (always in camelCase) like the class name (always in PascalCase) in some argument of some function or subroutine, like this:

Sub CalculateSomething (ByRef myClass as MyClass)

I changed the name of the class and I resolved the problem. (for example MyClass became MyAaaClass)
I write this for your future use or release.

Thank you for everything.