title: asp.net MVC should a View-Model Encapsulate Domain-Model?
body: <p>I've see a lot of MVC examples where domain-objects are passed directly to views, this will work fine if your view is simple.</p>
  
  <p>The common alternative is to have a view-model which has all the same properties as your domain-model + any extra properties your view may need (such as 'confirmPassword').</p>
  
  <p>Before doing too much reading and before discovering AutoMapper I started creating my own variant of view-model where the domain-object (or multiple domain objects) are simply properties of the view-model.</p>
  
  <p>Have I done a bad thing? What problems or benefits could be derived from this approach?
  Under what circumstances might this way of doing things work well?</p>