Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Thanks... so are you saying that ideally one would use a single DBContext instance from the initial creation of the session shopping cart through check-out (or abandonment of the cart)? If that's what you mean, then I can certainly see where an ASP.NET MVC application might not lend itself to that. Commented Jan 24, 2015 at 21:12
  • 1
    I am saying that session state would be handled some other way than holding a DBContext open. The SESSION state might be persisted to the database between pages, for example. Or, it can be held in a browser cookie or hidden page element. Commented Jan 24, 2015 at 21:35
  • OK, I get it. It just seems strange (to me) to say that the request/response model "prevents the default functionality of Entity Framework from working". I would have just said something like "you can't leave DBContexts open for subsequent requests in the same session, and that presents some architectural issues". Commented Jan 24, 2015 at 21:39
  • 1
    You can, but then you'd have to store it as a member variable of the repository or service layer. You'd have service layer methods representing incomplete transactions (not units of work), and that wouldn't be good either. Commented Jan 24, 2015 at 21:39