Repository Pattern.

First of all, Repository Pattern is conceptually separate from Linq vs Entity. You could use Repository to manage data from all sorts of sources, whether they be entity, linq, ADO.NET, file system data storage, xml, webservices, whatever. A repository is simply a collection of methods that return usable data objects and abstract the business layer from the data layer.

Entity Framework already implements a repository pattern. DbContext is your UoW (Unit of Work) and each DbSet is the repository. Implementing another layer on top of this is not only redundant, but makes maintenance harder.

Hi Rohan,

 

It is always good EF with Repository pattern. Please find few good examples,

 

https://www.c-sharpcorner.com/UploadFile/8a67c0/repository-pattern-with-Asp-Net-mvc-with-entity-framework/

https://docs.microsoft.com/en-us/aspnet/mvc/overview/older-versions/getting-started-with-ef-5-using-mvc-4/implementing-the-repository-and-unit-of-work-patterns-in-an-asp-net-mvc-application