Comments
Sort by recent activity
I disagree with you on your analysis regarding "opt-in" "opt-out". The standard ObfuscationAttribute also works on the basis of opt-out. You can only specify to "Exclude" elements from obfuscation (which is the same as "not obfuscate") with the attribute. So it's basically a "DoNotObfuscate" Attribute with a different name. Other obfuscators that use the standard attribute work just the same as your system. The other way around is not feasible. It's not always possible to enforce obfuscation to just a subset of members (like obfuscate a class name but not the inner classes' names).
As far as I understand translating the standard attribute to your proprietary attribute should be trivial and you would do your customers the favor and enable them to use your tool with third party libraries. You could even write an attribute processing tool that ildasms the dll, translates the attributes and does the bundling again. / comments
I disagree with you on your analysis regarding "opt-in" "opt-out". The standard ObfuscationAttribute also works on the basis of opt-out. You can only specify to "Exclude" elements from obfuscation ...