title: Why it's not a good idea to pass entities as Models in MVC?
body: <p>We're developing a pretty large application with MVC 2 RC2 and we've received some feedback on the way we're using the Entity Framework's Lazy Loading. </p>
  
  <p>We're just getting the entities in the controller and sending them as models to the Views, that is causing that the view code asks the Database for the navigation properties we are using in it. We have read about this and it appears is not a good design, but we were wondering why?</p>
  
  <p>Can you help us understand this design problem?</p>
  
  <p>Thanks!</p>