@Html.ValueFor(x=>x.PropertyName)
@Model.PropertyName
It seems like these two Razor commands do the exact same thing. Is there any special circumstance or benefit of using one over the other?
The Html. HiddenFor<TModel, TProperty> extension method is a strongly typed extension method generates a hidden input element for the model property specified using a lambda expression. Visit docs.microsoft.com to know all the overloads of HiddenFor() method. Example: HiddenFor() in Razor View.
ASP.NET MVC includes the method that generates HTML input elements based on the datatype. The Html. Editor() or Html. EditorFor() extension methods generate HTML elements based on the data type of the model object's property.
In MVC, HTML Helper can be considered as a method that returns you a string. This string can describe the specific type of detail of your requirement. Example: We can utilize the HTML Helpers to perform standard HTML tags, for example HTML<input>, and any <img> tags.
@Html.ValueFor(x => x.PropertyName)
invokes a lot a code and reflection under the hood.
It will allow you to customize the way the value is presented, and then have a consistent format across your whole site.
For example, if your property is decorated with DisplayFormatAttribute
.
@Model.PropertyName
is literally getting the value of the property directly, calling ToString() on it, and HTML escaping the result. No other formatting will take place.
To illustrate, you might see this:
[DisplayFormat(DataFormatString="{0:C}")]
public decimal PropertyName = 1234.56;
@Html.ValueFor(x => x.PropertyName) => "£1,234.56"
@Model.PropertyName => "1234.56"
ValueFor
will invoke the template that exists for rendering the type that the property has. By default this template may be as simple as ToString()
, but you can define anything as the template.
@Model.PropertyName
will simply present the value as string.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With