Preemptive mapn.xml
Ben1628
Posts: 12
Is there something in smartassembly that is similiar to preemptive mapn.xml.
I think that will help one to identify the new name of the method that one is interested in, in case one needs to do further processing to that method after obfuscation, or making sure the the method is obfuscated to their satifisfaction using reflector.
I think that will help one to identify the new name of the method that one is interested in, in case one needs to do further processing to that method after obfuscation, or making sure the the method is obfuscated to their satifisfaction using reflector.
Comments
If you do need to do post processing on the assembly where you need to know the obfuscated name you can use the "[ObfuscateTo( string )]" attribute, although I'll admit it is not the most friendly method.
I don't see any doc on "[ObfuscateTo( string )]".
Is this how we do it?
[ObfuscateTo(human)]
void anymethod()
{}
Do we need to enclose human with ""
The string is a standard .NET System.String so it is enclosed in "", and you can do anything you can do with a string constant (e.g. "\u0001Hello" )
The other attribute which you would probably want to use alongside [ObfuscateTo(..)] is [ObfsucateNamespaceTo( string )] this, unsurprisingly, specifies the name to obfuscate the namespace of the type to.
There is a full list of all the 15 attributes you can apply in the SmartAssembly.Attributes.cs or SmartAssembly.Attributes.vb which are in the "Attributes" folder where you installed SmartAssembly ("C:\Program Files\Red Gate\SmartAssembly 5\Attributes" by default).
Doesn't seem to do anything. I use Reflector to reverse engineer the exe, and there is no method with human.
btw,
apply ObfsucateNamespaceTo( string )]
namespace whatever
generate compile error
[ObfuscateNamespaceTo( string )] needs to be applied to a class, struct, enum or interface, otherwise you will get a compiler error.
I want to obfuscate using Unicode unprintable characters and advanced renaming alogorithm
and then on filed Name Mangling (I don't think that make any difference), I choose
I want to use advanced renaming, so that fields of a different type can have the same name
However, I still cannot locate my method.
may be you can just show me an example.
No the field name managling shouldn't make any different in this case.