ApplyToMembers not work in ObfuscationAttribute(Exclude = true, ApplyToMembers = true)]

[ahmedosama007]

ApplyToMembers does not work in ObfuscationAttribute(Exclude = true, ApplyToMembers = true)], it should exclude all class members from certain protection modules

[ahmedosama007]

The workaround is to add the attribute to each property/method of the class

For example [Obfuscation(Exclude = false, Feature = "-rename")] to exclude from Rename protection

yck1509#525

[mkaring]

Yes, but this is a proper hassle. Especially if the class contains a lot of members. I'll try to fix this for the 1.x and the 2.x releases.

[KvanTTT]

@ahmedosama007, unfortunately, it does not work for properties, only for fields. I guess this is due to properties contain autogenerated getter and setter.

[mkaring]

@KvanTTT: That did not work at all properly. A type with this specific attribute should forward it's altered configuration to all the members.

@ahmedosama007: I think I fixed the issue and the version containing the fix can be downloaded here. I would appreciate some feedback if it works for you now.

[ahmedosama007]

@mkaring Thanks, I confirm that the issue was fixed, ApplyToMembers = true is now can exclude all class members from certain protections specified by attribute parameter Feature

Thanks for fixing this. please accept my coffee and have a nice day

[KvanTTT]

@mkaring in your build renaming of public members and types are disabled by default. It differs from previous behavior. Is this made intentionally?

[mkaring]

@KvanTTT Not exactly sure what you are talking about.

[KvanTTT]

renPublic is false in your build. In the previous version, it was true.

[mkaring]

@KvanTTT If you have a look here you find the behaviour of renPublic unchanged for some time in the 1.x branch. In the 2.x line this parameter is gone and that it intentional. It will be replaced with something more clearly structured.