ASP.NET MVC: ViewModels versus Domain Entities

Question

I\'m building a concept application with MVC 3 in an attempt to learn its ways. I\'ve previously done some very heavy-duty applications in WebForms, using an n-tier approach

Answer 1

My approach is that a ViewModel model should be associated to a single view (or least a set of related views), and is usually a sub-set of your domain model. I see a ViewModel as responsible for UI validation, where as your domain object is responsible for business rule validation.

As for mapping between the two, highly recommend using Automapper which can automatically map properties based on conventions, it's a huge time saver.