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.

Required fields*

10
  • This deserves a better answer than I've got time to write at the moment. However when I did this I had an ISessionManager which provided the current UoW on request and was a dependency of the repositories. The SessionManager implementation could be stored in memory or http context depending on the application. Commented Aug 24, 2018 at 9:56
  • 1
    @Liath: It sounds interesting, but don't think I'm fully getting what you mean. An extended answer would be welcome if and when you could find the time (or if someone else wishes to elaborate) Commented Aug 24, 2018 at 9:57
  • If I was doing this i would have each UOW have it's own instance of each required repository, scoped to the UOW life cycle just as the DbContext is. Then when the repositories are created you just inject the DbContext into the constructor. Commented Aug 24, 2018 at 11:27
  • @user1450877: Each UOW can have its own repository objects, I have no issue with that. It's actually a requirement, since all the repositories of a single UOW should share the same context, and the repositories of another UOW should share a different context. That means that two UOWs cannot logically use the same repository (as they need to have different contexts) "you just inject the DbContext into the constructor" That is exactly what the question is about, I'm asking how to correctly achieve this. Commented Aug 24, 2018 at 12:30
  • @Flater scope the DBContext to the lifecycle of your unit of work planetgeek.ch/2010/12/08/… Commented Aug 24, 2018 at 15:38