Using Dependency injection to initialise Entity Framework model?

Question

So i started looking into Dependency Injection and Ioc Containers. From what i know DI is used to avoid tighly coupling the classes or avoid creating the depending object out of the consumer class. But isnt it unnecessary to use DI if we are using that object only in one class? Now my problem is how do i initialize my Entity model with unity? Currently i use constructor injection as usual to initialise my Entity model as

public class Food
{
    private FoodContext _foodContext

    public Food(FoodContext food)
    {
        _foodContext=food
    } 
}

Now here FoodContext is my entity framework model, how do I initialise with unity? I may want to replace the model with another in future, so it may become a headache to find and replace all the reference across the entire solution. So in order for doing that, am I going to create an interface first? I mean that autogenerated class contains lots and lots of properties and methods. that doesn't seem right.

So what is the normal practice of doing this?

HichemSeeSharp · Accepted Answer · 2013-01-28 06:58:56Z

1

To achieve that, take a look at the Repository pattern The main Idea of Repository pattern : It abstracts the DataProvider using an interface and called using dependency injection that leads to two main benefits : Low coupling and Testability.

edited Jan 28, 2013 at 6:58

answered Jan 20, 2013 at 16:53

HichemSeeSharp

3,3483 gold badges25 silver badges44 bronze badges

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

1 Comment

Muhammed Irshad Over a year ago

exactly.Thanks bro, its a bit complicated, but i'm diving in.

Collectives™ on Stack Overflow

Using Dependency injection to initialise Entity Framework model?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related