Inject Ordering Context rather than Unit Of Work in Transaction Behavior to create Transaction in Db

[zakaria-hajeid]

Hello, I have a question about why you depend on Ordering context in Transaction Behavior To (BeginTransactionAsync)
Why the transaction operation are put in ordering context ? in this case you can use the data access layer in application layer
why not depend on UnitOfWork abstraction to create transaction and manage the transaction ?

[aymancs85]

i have the same question

[Vinko90]

I have the same question as well, would be nice if someone would clarify this. In our company we keep copy-pasting this Transaction behavior in all the repo we have and I don't understand how we can make this generic.

I have a DomainContext which is a generic implementation of the "OrderingContext". So in every domain repository we have, we create a db context and inherit this DomainContext.
However MediatR is not able to resolve the generic DomainContext.