title: Entity Framework 6 Code First - Is Repository Implementation a Good One?
body: <p>I am about to implement an Entity Framework 6 design with a repository and unit of work.</p>
  
  <p>There are so many articles around and I'm not sure what the best advice is: For example I realy like the pattern implemented here: for the reasons suggested in the article <a href="http://codefizzle.wordpress.com/2012/07/26/correct-use-of-repository-and-unit-of-work-patterns-in-asp-net-mvc/">here</a></p>
  
  <p>However, <code>Tom Dykstra (Senior Programming Writer on Microsoft's Web Platform &amp; Tools Content Team)</code> suggests it should be done in another article: <a href="http://www.asp.net/mvc/tutorials/getting-started-with-ef-5-using-mvc-4/implementing-the-repository-and-unit-of-work-patterns-in-an-asp-net-mvc-application">here</a></p>
  
  <p>I subscribe to <code>Pluralsight</code>, and it is implemented in a slightly different way pretty much every time it is used in a course so choosing a design is difficult.</p>
  
  <p>Some people seem to suggest that unit of work is already implemented by <code>DbContext</code> as in this <a href="http://social.msdn.microsoft.com/Forums/en-US/435bf3a3-a358-41cf-a1b0-9f4387dcf5f2/is-unit-of-work-functionality-already-available-inside-the-dbcontext-in-ef-5?forum=adodotnetentityframework">post</a>, so we shouldn't need to implement it at all.</p>
  
  <p>I realise that this type of question has been asked before and this may be subjective but my question is direct:</p>
  
  <p>I like the approach in the first (Code Fizzle) article and wanted to know if it is perhaps more maintainable and as easily testable as other approaches and safe to go ahead with?</p>
  
  <p>Any other views are more than welcome.</p>