I'm working on a website that has fairly extensive user account requirements, so I figured that I would use some of the template code that ASP.NET MVC2 project generate with a new project. That is when I noticed that the models used in the built in models are very "form" centric. That is, there is a LogOnModel and RegisterModel (both of which contain UserName and Password). I have always defined my model in terms of the business model (e.g., a User model with a UserName and a Password), and then projected out specific properties for a form, and let the ModelBinder fill in the model on form submissions. What is the advantage of having a model that aligns to the form, instead of to the conceptual object?
Thanks, Erick -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
