ossecsoft / obfuscar

Obfuscation .NET project
0 stars 2 forks source link

Obfuscation of methods by parameter #41

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
In WPF, nearly all methods being called from XAML have specific arguments: For 
instance, anything _Click has a parameter coming from RoutedEventArgs. If it 
were possible to filter based on parameters derived from certain types, this 
would be a great way to eliminate the necessary method names from obfuscation.

Also, is there a way to exclude only the method name? For WPF, I really only 
need to be able to prevent obfuscation of (a) the method name, (b) public 
properties, and (c) methods containing RoutedEventArgs, more or less. There are 
a few exceptions, but that's 99% of it.

Original issue reported on code.google.com by xoc...@gmail.com on 11 Feb 2011 at 4:05

GoogleCodeExporter commented 8 years ago
Creating a new obfuscation rule to exclude methods based on the type of their 
arguments, seems too special to me. But, as you wrote, the method names have 
common postfixes. You could check for methods ending with "_Click".

> Also, is there a way to exclude only the method name?

I am not sure what you mean. <SkipMethod> only skips the obfuscation of method 
names.

I changed the issue's label from Type-Defect to Type-Enhancement.

Original comment by webbi...@gmail.com on 11 Feb 2011 at 9:09

GoogleCodeExporter commented 8 years ago
Well, what I mean is, consider for WPF's case...

Essentially all callbacks from WPF have a type from WPF's assembly in them. 
Usually RoutedEventArgs. So this would not be particularly special - I would 
apply it to all methods in my project.

Original comment by xoc...@gmail.com on 12 Feb 2011 at 12:06

GoogleCodeExporter commented 8 years ago
I am not sure if this has been further investigated, but I will spare some time 
later to explore the WPF area on my own fork at 
https://github.com/lextm/obfuscar

Original comment by lextu...@gmail.com on 28 Apr 2013 at 7:44