Home/ Questions/Q 8617591
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T05:53:51+00:00

Razor 2 (which ships with MVC4) doesn’t seem to be fully backwards compatible with

  • 0

Razor 2 (which ships with MVC4) doesn’t seem to be fully backwards compatible with Razor 1 (from MVC3).

Since upgrading, I found an error:

The “td@Html.Raw(count” element was not closed. All elements must be either self-closing or have a matching end tag.

The code that caused this was:

<td@Html.Raw(count == null ? null : " class='has-item'")>

What is the solution to this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The Razor parser was re-written for MVC 4, presumably because:

    The HTML5-specs clearly states that unclosed HTML-tags are supported, but Razor v1 didn’t have an advanced enough parser to support this. Razor v2 now supports this with the elements listed in W3C’s spec.

    The simplest solution here is to add a single space before the @ symbol:

    <td @Html.Raw(count == null ? null : " class='has-item'")>

    However, conditional attributes in Razor with MVC 4 have a more elegant syntax.

    <td class="@(count == null ? null : "has-item")">

    When an attribute value resolves to null, the attribute is omitted from the element. So the output of this markup is either:

    <td>

    …or…

    <td class="has-item">
    • 0