使用@Html.DisplayFor偶现返回ViewBuffer而非格式化值的问题

I’ve run into this exact frustrating issue before—especially with date formatting scenarios where you expect a clean string like "30 jan 2019" but get that cryptic Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ViewBuffer text instead. Let’s break down what’s happening and how to fix it:

Root Cause #

The core problem is that @Html.DisplayFor returns an IHtmlContent object, not a raw string. When you use this method in contexts where Razor can’t properly handle IHtmlContent (like concatenating it with a string, passing it to a string-expecting method, or nesting it incorrectly inside other helpers), the framework falls back to calling ToString() on the underlying ViewBuffer—which just outputs the type name instead of your formatted value.

Solutions #

1. Use DisplayFor directly in Razor (simplest fix) #

Always output DisplayFor as a top-level Razor expression, no unnecessary code blocks or string operations wrapped around it. For example:

<!-- Correct: Renders the formatted date properly -->
@Html.DisplayFor(m => m.MyDateProperty)

<!-- Wrong: Triggers ToString() on IHtmlContent and shows the ViewBuffer text -->
@("Event date: " + Html.DisplayFor(m => m.MyDateProperty))

If you need surrounding text, use Razor’s implicit output instead:

Event date: @Html.DisplayFor(m => m.MyDateProperty)

2. Convert IHtmlContent to string when necessary #

If you must work with the formatted value as a string (for custom logic, for example), use a StringWriter to properly render the IHtmlContent:

@{
    using (var writer = new StringWriter())
    {
        Html.DisplayFor(m => m.MyDateProperty).WriteTo(writer, HtmlEncoder.Default);
        string formattedDate = writer.ToString();
        // Use formattedDate in your custom logic here
    }
}

3. Verify your DisplayFormat attribute #

Double-check that your model property has the correct formatting configuration to ensure DisplayFor knows how to render the date. For your "30 jan 2019" example:

using System.ComponentModel.DataAnnotations;

public class EventModel
{
    [DisplayFormat(DataFormatString = "{0:dd MMM yyyy}", ApplyFormatInEditMode = false)]
    public DateTime EventDate { get; set; }
}

This ensures the display helper applies the exact format you expect every time.

4. Avoid nesting DisplayFor inside other helpers/tag helpers #

Nesting DisplayFor inside components like custom tag helpers or Html.Raw can sometimes trigger this issue. Keep it as a direct child of your markup elements whenever possible.

内容的提问来源于stack exchange，提问作者user3022476