title: Generic Repository With EF 4.1 what is the point
body: <p>As i dig deeper in to the DbContext, DbSet and associated interfaces, I am wondering why you would need to implement a separate "Generic" Repository around these implementations?</p>
  
  <p>It looks like DbContext and IDbSet do everything you need and include the "Unit Of Work" inside DbContext.</p>
  
  <p>Am I missing something here or does it seem people enjoy adding another layer of dependency for no reason.</p>