We have some Well-Attributed DB code, like so:
[Display(Name = \"Phone Number\")]
public string Phone { get; set; }
Since it is quite gen
You could jump through hoops and use an additional attribute to define the variable portion, but that would be quite a bit of work compared to what it would produce. There's no simple way to accomplish what you're after.
Everything inside an attribute must be known to the compiler at compile-time. Variables are inherently variable (!) so can't be used in attributes.
If you can use a code generation tool, you'd be able to dynamically inject different (constant) values into each derived class.