Renaming flows through your expression trees
A lambda like c => c.Name does not compile to a method body when its type is Expression<T> — it compiles to factory calls that encode the property access as a metadata token, not a string. Renaming rewrites that token with the member, so the tree still resolves and the compiled lambda still runs. The trap is Member.Name: it returns the live metadata name, so any library that derives a column, a JSON key, or a validation message from x => x.Prop silently starts emitting the obfuscated name. Here is the exact IL, why renaming reaches inside the tree, and how to keep a name-derived contract stable.
