ASP.NET MVC ModelBinder bug: Binding request varia

Question

I am using MVC 3 final RTM.

Given

This route:

context.MapRoute(
    "Blog_Posts",
    "Blog/Posts/{id}/{slug}",
    new { controller = "Posts", action = "Index", slug = UrlParameter.Optional }
);

And on a post's page, e.g. /blog/posts/2/some-slug I bind a partial view with a Comment model:

@Html.Partial("_CommentEditor", new Comment())

And Comment has a public int Id {get; set;}.

And in the partial view, I have this:

@Html.HiddenFor(comment => comment.Id)

Why does it display this?

<input type="hidden" value="2" name="Id" id="Id" data-val-required="The Id field is required." data-val-number="The field Id must be a number." data-val="true">

And why when I change Id on Comment to CommentId does it correctly have a value of 0?

Me thinks the default model binder is binding to the {id} of the route.

Answer 1

It is a bug or it might not because of below implemented logic;

In Asp.NET MVC, a View engine uses ViewData (it is variable and its type is "ViewDataDictionary"). And this ViewData has 2 properties "ModelState" that holds routing values, and "Model" that holds our actual model object.

1. A View engine looks into "ModelState" object retrieving value of a property.
2. If found in step 1 then return value.
3. Else looks into "Model" object to retrieve value for a property.

In above case, route has property "id" and its value are saved in "ModelState" so it return value from "ModelState" instead of binded model.

For above scenario, any input control renders with unexpected value.

Resolution is:

<div class="postData" value='@Model.Id'/>

//use below jquery function to retrieve data
var postedData = $('.postData');

Answer 2

Try:

Try @Html.Partial("_CommentEditor", new Comment{Id = 0}) 

Answer 3

If you're using linq to sql, fields marked as provided by database cannot be set manually.

Answer 4

That's happens because when you are using HTML helpers such as HiddenFor they first look at route data and model state and after that in the model. So they find in your route data a parameter id=2 and use this value instead of the id=0 in the model you are passing.