Question

I’m currently just starting to implement Dependency injection so I can start testing my code and have come across an issue many of times that I can’t figure out.

My current case scenario:

I have a single class ( foo.cs ) that is active the whole time a windows service is running. Its responsible for polling the db for new messages then sending them out and update the db to reflect the success of the send.

My issue is that foo.cs has a dependency for the data access (Message Repository – a linq-to-sql data context) so its injected via the constructor and its life time scope is the same as foo. Everywhere I’m reading it says that a data context lifetime should be a single unit of work. So its like I need to inject the actual type I want to use and constructed it every time I want to do a single unit of work in foo rather than passing in a already constructed Repository that stays alive for the entire duration of the service.

Answer 1

One possibility: Don’t give the Foo class a data context directly during construction, but rather give it a data context ‘factory’ class/interface that implements a method that creates a fresh data context on each invocation.

**EDIT**

In case my description is unclear, here’s a sketch of what I mean:

interface IDataContextFactory
{
    ??? CreateContext();
}

class DataContextFactory : IDataContextFactory
{
    public ??? CreateContext()
    {
        // Create and return the LINQ data context here...
    }
}

class Foo
{
    IDataContextFactory _dataContextFactory;

    public Foo(IDataContextFactory dataContextFactory)
    {
        _dataContextFactory = dataContextFactory;
    }

    void Poll()
    {
        using (var context = _dataContextFactory.CreateContext())
        {
            //...
        }
    }
}