Feb 29, 2012 10:46 AM|BrockAllen|LINK
I don't see anything alarming in your model.
Actually, why do you need to use TryUpdateModel? Do you need to be in control of the object creation? That's the main reason to use UpdateModel/TryUpdateModel. Also by passing the FormCollection's value provider, you're narrowing what potential inputs from
the http request to use for model binding, meaning no query string or route values will be used. Maybe that's ok, maybe that's not.
Maybe just try accepting the model as the paramater to your action method and avoid calling TryUpdateModel.