Obfuscation cannot handle reflections about confuserex HOT 5 CLOSED

I can change the renaming to cover this simple case. How ever in general you should't allow ConfuserEx to rename a method you are accessing using reflection, by disabling renaming using the ObfuscationAttribute like this:

[Obfuscation(Exclude=false, Feature="-rename")]
void HelloWorld() {
  …
} 

Or by adding a rule to the Confuser Project (*.crproj) that disables renaming for the specific method.

from confuserex.

@Mighty00 The enhancement has been implemented and is supported in this feature build. It would be great if you could confirm that it works in your specific case. The improvement will be part of the 1.2 release.

from confuserex.

Renaming works good now. But you should also add support for GetILAsByteArray reflection method, since other protection modules could change the bytes of a method body

from confuserex.

GetILAsByteArray is still working, as refetching the required MethodInfo is now working again. Detecting exactly what you are doing with that MethodInfo is very difficult. Also the function will still work, but it will receive the obfuscated code. If you code is relying on the IL code of a method being not obfuscated, that is a method you really should exclude from obfuscation.

from confuserex.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from confuserex.