How to avoid references to Entity framework in multiple projects

Question

I want to encapsulate Entity Framework in one project. This project will do DB access alone. When updating, I want to map a domain model to EF. The purpose is that other layers of the solution should have no knowledge of infrastructure.

My problem is that I need to reference EF in my "caller" project to make it work.

Is there a way to avoid this?

Solution - ConsoleProject - EntityFrameworkProject (EF from Nuget)

Have you tried Repository design pattern with Unit Of Work ? — captainsac
– captainsac, Commented Apr 29, 2015 at 10:47
if you generate your POCO objects for EF in your repository project, you only need a reference to this project and no EF reference is required in your "caller project"? — Vincent De Smet
– Vincent De Smet, Commented Apr 29, 2015 at 10:50
Create project responsible for database connection and create repositories (Unit Of Work is also good idea). Create some interfaces with DTOs and your other projects shouldn't contain reference to EF. — Marcin J
– Marcin J, Commented Apr 29, 2015 at 10:53

René Sackers · Accepted Answer · 2017-06-01 15:33:04Z

3

With EF6 and code based configurations, this is now possible.

[DbConfigurationType(typeof(MyDbContextConfiguration))]
internal class MyDbContext : DbContext
{
    public DbSet<MyModel> MyModels { get; set; }
}

internal class MyDbContextConfiguration : DbConfiguration
{
    public MyDbContextConfiguration()
    {
        SetProviderServices("System.Data.SqlClient", SqlProviderServices.Instance);
    }
}

If you configure your database in Project A as above, then only Project A needs to reference EntityFramework, and any project that references it, like Project B will not try to find the provider in its own assembly.

Expose your repositories in Project A, and add a <connectionStrings> configuration in Project B, and it should work flawlessly.

edited Jun 1, 2017 at 15:33

answered Jun 1, 2017 at 15:22

René Sackers

2,6734 gold badges29 silver badges44 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Community · Accepted Answer · 2017-05-23 12:15:41Z

1

I used this approach: https://stackoverflow.com/a/22970805/3874212

I reference the EntityFramework.SqlServer.dll only in the Console startup project.
I install entity Framework in my other project.
I create my model from DB in EF project
I move the connection string from the app.config in EF project to the Console project.

edited May 23, 2017 at 12:15

CommunityBot

11 silver badge

answered Apr 29, 2015 at 12:42

redlaz

1214 silver badges10 bronze badges

Comments

Ondřej · Accepted Answer · 2016-02-19 12:41:26Z

0

Unfortunately it is not possible for some strange reason. You must include EF package in client application too, not only in data access library.
It is possible to include only that DLL redlaz mentioned, but by doing this you are cooking lot of potential problems with versions.
Just overcome all reluctance and add EF package to your client application too.

answered Feb 19, 2016 at 12:41

Ondřej

1,6731 gold badge18 silver badges30 bronze badges

Collectives™ on Stack Overflow

How to avoid references to Entity framework in multiple projects

3 Answers 3

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related