Ninject, DbContext & Windows Service - New Instance Each Time Thread Runs?

Question

I\'m current writing a Windows Service which connects to an existing service layer using Entity Framework (DbContext), and Ninject to inject the Respositories and DbContext inst

Answer 1

See here for the answer

In Ninject2, you can do this by:

Bind<IService>().To<ServiceImpl>().InScope(ctx => ...);

The object returned by the callback passed to InScope() becomes the "owning" object of instances activated within the scope. This has two meanings:

1. If the callback returns the same object for more than one activation, Ninject will re-use the instance from the first activation.

2. When the object returned from the callback is garbage collected, Ninject will deactivate ("tear down", call Dispose(), etc.) any instances associated with that object.

For example, the callback used for InRequestScope() is:

ctx => HttpContext.Current

Since HttpContext.Current is set to a new instance of HttpContext on each web request, only a single instance of the service will be activated for each request, and when the request ends and the HttpContext is (eventually) collected, the instances will be deactivated.

The object returned by the callback can also implement INotifyWhenDisposed, an interface from Ninject, if you want to deterministically deactivate the "owned" instances. If the scoping object implements this interface, when it is Dispose()'d, any instances it owns will be deactivated immediately.