ASP.NET Unit of Work With Entity Framework

Dec 09, 2015 reading time 6 minutes

ASP.NET Unit of Work With Entity Framework

I implemented a solution for the ASP.NET Unit Of Work with Entity Framework (see this post) and put all this into a NuGet-Package. And finally: Here it is!


Nuget: UnitOfWork by Offering.Solutions

Github: OfferingSolutions UnitOfWork with Entity Framework

This blog post has a sample-solution attached. Feel free to look into it. But before you do, let me explain this package a bit. It will use the UnitOfWork, you will be able to use GenericRepositories and Customrepositories and everything is cached so that if you use the repositories in one using they only have to be created once.

I won’t go into details about the sense of the UnitOfWork-thing, but I want to give you code-examples how you can start with this in a few minutes of your time.

If you want to work with the UnitOfWork in this NuGet-Package you will have two different possibilities:

  1. Use generic repositories
  2. Extend the generic repositories to use your own functions additional to the given CRUD-operations

I want to handle both cases in this post:

Lets start:

First of all you have to install the NuGet-Package. It will add you the needed dll you can work with.

1) Use generic repositories

The common case is that you have a DatabaseContext and DbSets of your entities stored in it. After adding the package, you can use the OsUnitOfWorkContext as follows

using (IOsUnitOfWorkContext unitOfWorkContext = new OsUnitOfWorkContext(new DatabaseContext()))
    Person person = new Person() { Age = 28, Name = "Fabian" };

    //Adding a new Entity, for example "Person"



    // Get all Persons
    List allPersons = unitOfWorkContext.GetAll().ToList();

    // Get all Persons with the age of 35
    List allPersonsOnAge35 = unitOfWorkContext.GetAll(x => x.Age == 35).ToList();

    // Get all Persons with the age of 35 ordered by Name
    List allPersonsOnAge35Ordered = unitOfWorkContext.GetAll(x => x.Age == 35, orderBy: q => q.OrderBy(d => d.Name)).ToList();

    // Get all Persons with the age of 35 ordered by Name and include its properties
    List allPersonsOnAge35OrderedAndWithThings = unitOfWorkContext.GetAll(
        x => x.Age == 35,
        orderBy: q => q.OrderBy(d => d.Name),
        includeProperties: "Things").ToList();

    // Get all Persons and include its properties
    List allPersonsWithThings = unitOfWorkContext.GetAll(includeProperties: "Things").ToList();

    // Find a single Person with a specific name
    Person findBy = unitOfWorkContext.GetSingle(x => x.Name == "Fabian");

    // Find a single Person with a specific name and include its siblings
    Person findByWithThings = unitOfWorkContext.GetSingle(x => x.Name == "Fabian", includeProperties: "Things");

    // Find a person by id

    //Update an existing person

    //Add or Update a Person

    //Deleting a Person by Id or by entity

2) Use extended repositories

If you want the normal repository to extend a bit with your own functions, this is also possible. Everything you have to do is writing your own repository. You can even overwrite the normal CRUD-Methods to do whatever you like in there.

Attention to inherit it from the “IRepositoryContext” respectively the “RepositoryContextImpl”. The code should look like this:


public interface IPersonRepository : IRepositoryContext<Person>
    void MyNewFunction(int id);


public class PersonRepository : RepositoryContextImpl<Person>, IPersonRepository
    public PersonRepository(DbContext dbContext)
        : base(dbContext)


    public void MyNewFunction(int id)
        //Do Something

You can then use it with

using (IPersonRepository personRepository = new PersonRepository(new DatabaseContext()))
    personRepository.Add(new Person());
    List<Person> persons = personRepository.GetAll();

With this you can build your own repositories, and they are build up modular and are replaceable in an easy way.

That’s it. I think this is nice and smooth. I hope you can get along with it. Have fun.

See here and here for inspiration.

See also here for another related Blog Entry (when this Nuget was not released so far ;) )