Asp.Net MVC中@Html.ValidationMessage失效求助（复杂模型子集合场景）

Hey there, let's sort out this validation problem you're facing with your nested collection model. I get that using @Html.ValidationMessageFor isn't an option here since you're manually indexing into the collection, but there are a few reliable fixes to get those validation messages showing up correctly.

1. Double-Check the Validation Key Match #

First, make sure the key you're passing to @Html.ValidationMessage exactly matches both the name attribute of your text box and the key used in ModelState when adding errors. Sometimes even tiny typos or mismatched indexing can break this.

Your current code looks right on paper, but let's confirm:

@Html.TextBox("List[" + i + "].prop", Model[i].prop)
@Html.ValidationMessage("List[" + i + "].prop")

Ensure that in your controller, when you add a validation error, you're using the exact same key:

// Example for the 0th index item
ModelState.AddModelError("List[0].prop", "This field is required");

If the keys don't line up 100%, the validation message won't render.

2. Manually Add Client-Side Validation Attributes #

When you use TextBox instead of TextBoxFor, MVC doesn't automatically inject the client-side validation attributes (like data-val, data-val-required) that trigger client-side validation and link the message to the input. You'll need to add these manually in the HTML attributes parameter:

@Html.TextBox("List[" + i + "].prop", Model[i].prop, new {
    data_val = "true",
    data_val_required = "Please enter a value for prop",
    // Add other validation attributes here based on your model's data annotations
    // e.g., data-val-length = "The field must be between 2 and 10 characters",
    // data-val-length-min = "2",
    // data-val-length-max = "10"
})
@Html.ValidationMessage("List[" + i + "].prop")

This ensures both client-side validation works and the message is tied to the correct input.

3. Use an EditorTemplate (Recommended Approach) #

The cleanest and most maintainable fix is to use an EditorTemplate for your sub-model. This lets MVC handle all the naming and validation wiring automatically, so you don't have to mess with manual string concatenation.

Here's how to set it up:

1. Create a new partial view in Views/Shared/EditorTemplates (create the folder if it doesn't exist) named after your sub-model class (e.g., SubModel.cshtml).
2. In this template, use TextBoxFor and ValidationMessageFor like you would for a single model:

@model YourNamespace.SubModel

@Html.TextBoxFor(m => m.prop)
@Html.ValidationMessageFor(m => m.prop)

3. In your main view, replace your loop with a single call to EditorFor for the collection:

@Html.EditorFor(m => m.List)

MVC will automatically render an instance of the EditorTemplate for each item in the List collection, generating the correct name attributes (like List[0].prop, List[1].prop) and wiring up validation messages perfectly. This eliminates the risk of manual indexing errors and keeps your code cleaner.

Quick Check for Server-Side Validation #

If client-side validation is working for parent properties but not the collection, make sure your controller is properly validating the collection items. When you call ModelState.IsValid, MVC should validate all items in the collection if your sub-model has data annotations. If you're adding custom errors, double-check the key names as mentioned earlier.

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