'Lo again,
My dotfuscation efforts continue! Therefore, I am currently working on obfuscating a reasonable complex WPF application consisting of ~ 38 assemblies. Now that I have overcome performance issues ( Speed up the obfuscation process ), now I have moved on to testing the BAML obfuscation capabilities for Dotfuscator v4.10.
The problem is that it does not work - the generated errors (well, warnings) have the same form, for which I can not find anything on the network that discusses:
BamlAnalysis flagged something in Data Binding Path: SOMEFIELDNAME in SOMERESOURCEPATHTOBAML.baml for the following reasons: Could not resolve, may have to manually exclude.
Does anyone come across this and understand what he wants to change?
[EDIT:] Even setting up the manual eliminates the properties that it complains about, it doesn’t clear the warning ... and it doesn’t look like the basic BAML has been altered at all (at least not by visual inspection through the reflector).
[EDIT2:] You should also point out that Dotfuscator is a requirement here, so alternative tools probably won't help me.
source share