What is the best way to instantiate and dispose DbContext in MVC?

Question

MVC 3 + EF 4.1

I'm choosing between two approaches to deal with DbContext:

1. Instantiate in Application_BeginRequest, put it into HttpContext.Current.Items and dispose in Application_EndRequest.
2. Create disposable UnitOfWork (kindof wrapper for DbContext) and start each controller action with using(var unitOfWork = new UnitOfWork()) { ... }

Share your experience please: Which one would you prefer? what are pros and cons for each approach?

Answer 1

I would suggest you use a Dependency Injection framework. You can register your DbContext as per request

 container.RegisterType<MyDbContext>().InstancePerHttpRequest(); 

And inject it as a constructor parameter to the controller.

public class MyController : Controller {     public MyController(MyDbContext myDbContext)     {          _myDbContext = myDbContext;     } } 

If the registered type implements IDisposable then the DI framework will dispose it when the request ends.

1st approach: It is much more cleaner to use ID framework than manually implementing it. Further all your requests may not need your UoW.

2nd approach: The controller should not know how to construct your UoW(DbContext). Purpose is not reduce the coupling between components.