Open Ares-87 opened 4 years ago
Resource protection is currently an all or nothing deal. If it's enabled and ConfuserEx is able to resolve how the resources are accessed, they will be protected.
With XAML the problem is that renaming them is currently the only "protection" available. Hiding them from the BAML decompiler isn't possible, because WPF is accessing them the same way as the BAML decompilers. The XAML/BAML Syntax it self doesn't leave any room for modifications that make it harder to read but leave the result the same.
The only idea for XAML protection I got is to convert the XAML/BAML resources to C#/MSIL code and protect that. But that's not even on the road map as of right now.
I would like to rename specific resources and not all a unique solution with (resource protection 'resource'), is it possible to rename for example a single resource (in my case an image)? How can I protect xaml pages? Currently I can rename them but I can't protect them from the decompiler. Thank you.