title: ASP.NET MVC - Linq to Entities model as the ViewModel - is this good practice?
body: <p>Quick questions really.</p>
  
  <p>I am currently building a site using asp.net MVC and the entity framework. I have a couple of repositories in place which return entities or lists of entities. I am finding that in the majority of my pages I'm having to pull data from a variety of related tables. This is ok so long as I load up the related entities using  'include' in my queries - but is this good practice?</p>
  
  <p>Would it be better to create a custom viewmodel object that contains just the bits of info I need, or is there nothing 'wrong' with pulling an object graph that is perhaps 5 - 6 tables deep just to display what you need to in your view?</p>
  
  <p>Apologies if this question doesn't make too much sense. I may have fundamentally misunderstood how a model should be used here :)</p>
  
  <p>Thanks</p>