Obfuscating a WinForms app without losing your designer resources
WinForms has a trap WPF does not: the designer wires every form to an embedded .resources stream whose name is derived from the form type''s full name, and rebinds controls to data by property-name string. Rename the wrong thing and your icons vanish or a bound field goes blank — at runtime, with no compile error. Here is exactly what the designer emits, why renaming a Form type breaks ComponentResourceManager, and how to protect a WinForms build with Nebula.NET so the internals get hardened and the designer keeps working.



