Entity Framework code first in data access layer

Question

I am using N-layer architecure in my project. In the data access layer I use Entity Framework code first. When I fill an object in the DAL, dispose the context and transfer the object to the business layer, the navigation properties become null. I have no problem if I don't dispose the context, but my question is it good to dispose the context? If yes, how can I solve the problem when I transfer the object to the next layer (business), so that the navigational properties don't become null. My code in Data access layer:

public List<DomainObject.ContractCenter> GetAll()
{
    try
    {
        List<ContractCenter> contractCenters = new List<ContractCenter>();
        using (var context = new DBContext())
        {
            contractCenters = context.ContractCenters.ToList();
        }

        return contractCenters;
    }
}

Yakimych Yakimych · Accepted Answer · 2012-12-17T10:44:18

To answer your questions:

is it good to dispose the context?

Yes, the context should be as short-lived as possible (see @khellang's answer regarding UnitOfWork and IOC if you have a possibility to restructure your project and implement cleaner architecture).

how can i solve the problem when i transfer object to next layer

You need to eager-load the related collections (navigational properties):

public List<DomainObject.ContractCenter> GetAll()
{
    try
    {
        using (var context = new DBContext())
        {
            return context.ContractCenters.
                           Include(c => c.YourChildCollection1).
                           Include(c => c.YourChildCollection2).
                           ...
                           ToList();
        }
    }
}

Entity Framework code first in data access layer

2 Answers