title: In Asp.net MVC, is it advisable for viewmodels to derive from domain models?
body: <p>(I am using ASP.Net MVC, but this seems like a more generic MVC question)</p>
  
  <p>Say you have a domain model representing a person, and you have a view for editing a person.  Included in the Person domain object is a State of Residence property, and in the view you want a dropdown that lists states.  </p>
  
  <p>Is there any reason not to create a view model that derives from the domain model and simply includes properties for the UI spiciness the view requires?  If so, why would not not want to do this?</p>
  
  <p>TIA</p>