This is just for curiosity
Why does this code work:
Html.TextBoxFor(x => x.Age, new { @Value = \"0\"})
and this doe
My guess is that the MVC code is hard coded to look for Value
because a MS engineer intended you to always use PascalCase property names, since that's their typical convention and PascalCase avoids conflicts with non-contextual keywords such as class
. Notice how PascalCase properties get rendered in the HTML as lowercase.
The reason is not about value
being a keyword, since it's a contextual keyword in C# and only has special meaning (and thus turns blue in the IDE) in property getters and setters. It has no special meaning in the anonymous type passed to TextBoxFor
.
I'm not 100% sure but, that could be value
is a keyword in properties, readonly
isn't. Look at properties from MSDN.
InputExtensions.TextBoxFor special cases cases a few attribute names, among them value
(case sensitive). This is unrelated to C# keywords.
In particular the value obtained from the expression
parameter takes precedence of a property called value
you pass into the htmlAttributes
parameter.
Taking a look at your example:
If you use Html.TextBoxFor(x => x.Age, new { @value = "0"})
it will compile, but TextBoxFor
will override the value
attribute with the value x.Age
evaluates to.
If you use Html.TextBoxFor(x => x.Age, new { @Value = "0"})
it will compile, and you will get two entries in the attribute dictionary, one Value
that's "0"
, and one value
, that's x.Age
.
I expect the output to be something nonsensical like <input Value="0" value="..." type="text"/>
.