title: 3-tier MVC application using Unit of Work and Repository pattern
body: <p>I have a design problem while starting my MVC project. The example that i was following is on the following link: <a href="https://i.stack.imgur.com/kj2my.png" rel="nofollow noreferrer">Implementing the Repository and Unit of Work Patterns</a></p>
  
  <p><a href="https://i.stack.imgur.com/kj2my.png" rel="nofollow noreferrer">1</a>: <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" rel="nofollow noreferrer">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</a> .</p>
  
  <p>In there the unit of work and generic repository are in the data layer project. In my project they are also there, but from what i see they are making an instance from the unit of work class directly into the controller. </p>
  
  <p>Since i made the BAL project i am interested what i will have to change to the current design and what should the BAL project contain (some small code will help a lot).</p>
  
  <p>Here is a screenshot of my current project.</p>
  
  <p><img src="https://i.stack.imgur.com/kj2my.png" alt="My project"></p>