Repository Pattern.

Question

Please let me know is best way or not with EF with Repository Pattern

Sachin Singh · Answer

Yes, EF with Repository pattern is always good and saves a lot of time.

Muhammad Imran Ansari · Answer

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.

Jignesh Kumar · Answer

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

Repository Pattern.

Answers (3)