title: MVC: Data Models and View Models
body: <p>I've read some MVC advice in the past regarding models stating that you should not reuse the same model objects for the domain and the view; but I haven't been able to find anyone willing to discuss <em>why</em> this is bad.</p>
  
  <p>It is my opinion that creating two separate models - one for the domain, one for the view - and then mapping between them creates a lot of duplication, plus tedious mapping code (some of which might be alleviated by things like <a href="http://www.lostechies.com/blogs/jimmy_bogard/archive/2009/01/22/automapper-the-object-object-mapper.aspx" rel="noreferrer">AutoMapper</a>) that will likely be error prone.</p>
  
  <p>What makes having a separate model for the two concerns worth the trouble of duplication and mapping code?</p>