How renaming breaks Blazor component parameters - DEV Community
A Blazor Hybrid app ships its component assembly to the user''s machine, so it is worth obfuscating — but a component passes parameters through a name-keyed render tree, not a method call. This post reads the Razor-generated BuildRenderTree to show that every [Parameter] name travels as a string literal the renderer matches by reflection, which is why renaming one throws at first render, then scopes Nebula to keep those names and obfuscate everything else.