Open SoSuDresden opened 8 years ago
Why do you think that is not right? Internal classes are not accessable by outside assemblies (without reflection) so that means that it's safe to rename public properties in internal classes. That might be a problem if you are accessing these properties using reflection with hardcoded string. For example.: o.GetType().GetProperty("Property").GetValue(o, null);
For example, in small dialogs there I have internal classes (XAML-Dialog) with public properties, which I bind internal in the XAML code of the same class. The same is with classes they used for binding (only internal datatypes for list etc.). If I put this classes in internal classes, is the binding not possible (internal class X{ public class Y {...}...}).
I switched from Eazfuscator to ConfuserEx and have now with the same code more problems by renaming.
If a public property is in a internal class, so that property will be renamed. I think that is not right.