For this Demo I have created a fake Database+repository as below
public interface IDemoRepository
{
string[] GetUser
Make sure that your repository is bound to the request scope in Ninject if you want it to be disposed:
kernel.Bind<IDemoRepository>().To<DemoRepository>().InRequestScope();
You don't need to Dispose()
of you DbContext
, since it already manages all connections properly itself. Here's a quote from ASP.NET MVC Tip #34 – Dispose of Your DataContext (or Don’t):
The most important consequence of calling the DataContext.Dispose() method is that any open connections associated with the DataContext get closed. This might seem really important, but it’s not. The reason that it is not important is that the DataContext class already manages its connections. By default, the DataContext class opens and closes a connection automatically.
...
Most often, when you call the Dispose() method on the DataContext object, any database connection associated with the DataContext object is already closed. The DataContext object has closed the database connection right after executing the database query. So, the Dispose() method really doesn't have anything to do.