Obfuscating WinUI 3 apps: what x:Bind keeps rename-safe and the three strings that still break

A WPF obfuscation guide does not carry over cleanly to WinUI 3, and a UWP guide only partly applies, because the XAML compiler determines what survives renaming. WinUI 3 compiles x:Bind into C# inside the app's own assembly, so most bindings become metadata tokens that an obfuscator can rewrite correctly. Failures remain wherever WinUI or the developer's code still relies on strings, such as classic Binding paths, pages located by constructed type names, and manifest activation by literal class name. The article walks through the generated binding code to show why x:Bind is safe, while the string literal used in PropertyChanged notifications still ties the view to a property name. The analysis concludes that developers must check these string-based references manually when obfuscating a WinUI 3 app.