Any example C # project that allocates a separate level of data access (using EF) to the business logic level

I’m interested in looking at a small sample project that would highlight a good technique for dividing the level of data access (using the Entity Framework) to the level of business logic. In C # it would be nice.

That is, it will highlight how to transfer data between a layer without connecting them. That is, the assumption here is not to use the EF classes at the Business Logic level, and how to achieve this low combination, but to minimize the plumbing code.

+6
c # design-patterns entity-framework repository-pattern
source share

All Articles