Activity overview
Latest activity by javiersanag
Most of the classes that are not obfuscated derive from Window or from UserControl, so they are indeed related to WPF. In these classes none of the method names or field names are modified after obfuscation, and for instance, a simple private boolean keeps the name. Is this the expected behavior?
It seems that SmartAssembly has important limitations with WPF (maybe Microsoft's fault). Behavior like the one described above means that we need to move most of the logic to other non-WPF classes, but in many cases this is either not possible or it complicates code in an unnecessary way... / comments
Most of the classes that are not obfuscated derive from Window or from UserControl, so they are indeed related to WPF. In these classes none of the method names or field names are modified after ob...
jessica.ramos wrote:
Yes, that is strange. SmartAssembly does purposely skip obfuscation of certain types though -- are those objects that aren't getting obfuscated any of the following?
· Any type with the Serializable attribute specified will not be obfuscated
· Any type with a base class of System.MulticastDelegate will not be obfuscated
· Any type with the System.ServiceModel.OperationContractAttribute specified will not be obfuscated
· Any type with the System.ServiceModel.ServiceContractAttribute specified will not be obfuscated
· Any method with the System.Reflection.DefaultMemberAttribute specified will not be obfuscated
· Any type with an attribute starting with System.Xml.Serialization. set will not be obfuscated
We're not dealing with any of those types. I have activated the logging functionality, and I get many of these messages:
class [PresentationFramework]System.Windows.Controls.Grid GridClose excluded from obfuscation: Has a special base type ([PresentationFramework]System.Windows.Window)
Is WPF not supported? / comments
jessica.ramos wrote:
Yes, that is strange. SmartAssembly does purposely skip obfuscation of certain types though -- are those objects that aren't getting obfuscated any of the following?
· Any t...
Thanks for the reply. Unfortunately, I get the same behavior with version 6.6, even after specifying "ExcludePublicMembers = 0".
All my DLLs are merged into the main assembly, so I don't understand why they are not obfuscated in the expected way. It is especially worrying that the internal and private members keep their original names. Even the main .exe file has most private and internal members unchanged after obfuscation (this I don't understand why).
I hope something like this can be solved in the next version of SmartAssembly. / comments
Thanks for the reply. Unfortunately, I get the same behavior with version 6.6, even after specifying "ExcludePublicMembers = 0".
All my DLLs are merged into the main assembly, so I don't understand...
All method names and fields in DLL are not obfuscated
Hi!
I'm trying to obfuscate a DLL that contains some WPF and some public methods. On these classes, all method names and signatures remain intact, even when they are internal or private. Also, all ...