Take the 2-minute tour ×

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?

share|improve this question

2 Answers 2

up vote 16 down vote accepted

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.

share|improve this answer
From the documentation for ValueFor : "Provides a mechanism to create custom HTML markup compatible with the ASP.NET MVC model binders and templates." –  Dom May 24 '13 at 15:09

@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:

public decimal PropertyName = 1234.56;

@Html.ValueFor(x => x.PropertyName)  =>  "£1,234.56"
@Model.PropertyName                  =>  "1234.56"
share|improve this answer
That's a great example. Thank you! –  Buffalo May 28 '13 at 15:37

Your Answer


