tags:

views:

171

answers:

4

With this controller method: -

    [AcceptVerbs(HttpVerbs.Post)]
    public ViewResult Contact(Contact contactMessage)
    {
        return View();
    }

Why does this work...

public class Contact
{
    public string Name { get; set; }
    public string Email { get; set; }
    public string Message { get; set; }
}

<% using(Html.BeginForm()) { %>
<p>Name : <%= Html.TextBox("Name")%></p>
<p>Email : <%= Html.TextBox("Email")%></p>
<p>Message : <%= Html.TextBox("Message")%></p>
<p><input type="submit" value="Send Data" /></p>

But this doesn't?

public class Contact
{
    public string ContactName { get; set; }
    public string ContactEmail { get; set; }
    public string ContactMessage { get; set; }
}

<p>Name : <%= Html.TextBox("ContactName")%></p>
<p>Email : <%= Html.TextBox("ContactEmail")%></p>
<p>Message : <%= Html.TextBox("ContactMessage")%></p>
<p><input type="submit" value="Send Data" /></p>

Please don't tell me that field names are only partially identified ?

Trust me - All I did was add the text "Contact" to each of the fields in the object and each of the fields in the form. Its almost as if MVC got confused with the fields all starting with the same first 7 characters.

What gives ?

Can anyone shed any light on this ?

Paul.

+2  A: 

Is it possible the view auto-recompiled when you refreshed your browser, but the overall project hasn't been Rebuilt since you changed the property names?

Joel Mueller
Or he has no form tag. Can't see any other issue.
Arnis L.
Try the code and you will see the issue.
Darin Dimitrov
+1. Yeah- the project not being rebuilt was my first thought.
RichardOD
@RichardOD, unfortunately this is not where the problem comes from.
Darin Dimitrov
@Darin. Interesting- if I get the opportunity to try it out myself I will upvote your answer. I guess for now a good strategy is to debug the ModelBinder, if as you say there is a bug somewhere.
RichardOD
+3  A: 

I currently can't find any reasonable explanation as to why the second is not working. But it works if you change your action signature to look like this:

public ViewResult Index([Bind(Prefix="")]Contact contactMessage)

I suppose this has something to do with the DefaultModelBinder.


UPDATE: Ok, this starts to be really funny:

// Not working
public ViewResult Index(Contact contactMessage)

// Not working
public ViewResult Index(Contact contactmessage)

// Working
public ViewResult Index(Contact contact)

// Working
public ViewResult Index(Contact contactMsg)

// Working
public ViewResult Index(Contact abc)

Strange indeed!


UPDATE2:

Ok got it. You have a property called ContactMessage in your model and the variable name passed in the action is also called contactMessage. This is where the ambiguity comes from. No bug in the DefaultModelBinder. He can't bind at the same time to a property of type string and Contact, case closed :-)

Darin Dimitrov
Nice didn't try it in the end, but the Update2 makes perfect sense so +1.
RichardOD
Paul Stringer
@Paul- it's not a bug. The DefaultModel binder also tries to map id's to parameters, it doesn't know what your intentions are. It is certainly one of those things that catch you out though, that's why I upvoted your question!
RichardOD
A: 
<% using(Html.BeginForm()) { %>

is missing from your non-working example.

Or.. Maybe contactMessage parameter name is conflicting with the variable number in the form post.

badbod99
I removed the tags for brevity... Its in my form.
Paul Stringer
+1  A: 

Code your Textboxes like this:

 <%=html.TextBox("Contact.Name")%>

and you Action signature like this:

public ViewResult Index([Bind(Prefix="Contact")]Contact contactMessage)

I hope this helps and good luck

Nolo
Nolo: I didn't appreciate being able to do this - cool !!! :-)I'll try to remember this one.
Paul Stringer