ViewModel not matching model causes modelstate to be invalid

Question

I have a model class like this:

class Person {
   string FirstName, 
   string LastName,
   string ID
}

When I send the model to the browser via a GET, I send the data as a composite of two fields (e.g. FirstName.ToString() + LastName.ToString()) through an anonymous type.

The problem comes when I do a POST back to the server. Since the JSON is coming back as different from the model, it comes back as invalid through ModelState.IsValid() because my action method is expecting a List<Person> persons.

I really don't want to create a ModelViewModel duplicating code, because one field is causing the model to be invalid. Is there a way around this?

score 0 · Accepted Answer · answered Feb 04 '11 at 14:33

0

In this case, I would add DataAnnotations to the ViewModel class and change the Action to accept the ViewModel rather than the Model.

Once you validate that the ViewModel being passed to the Action is valid, you can parse the composite field back to into the First and Last names properly.

answered Feb 04 '11 at 14:33

Justin Niessner

242,243
40
408
536

I actually took your advice, but found it easier to just change the model before it even gets to the controller in my scenario. – Dan Mar 01 '11 at 20:33

ViewModel not matching model causes modelstate to be invalid

1 Answers1