unit-of-work

问题 Currently, I am trying to use Dapper ORM with Unit Of Work + Repository Pattern. I want to use Unit of Work as opposed to a simple dapper Repository due to the fact that my insert and updates require a degree of transaction processing. I have been unable to find any useful examples as most seem to use Entity Framework and have leakage issue within the Unit of Work. Could someone please point me in the right direction? 回答1: This Git project is very helpful. I started from the same and did some

问题 As i dig deeper in to the DbContext, DbSet and associated interfaces, I am wondering why you would need to implement a separate \"Generic\" Repository around these implementations? It looks like DbContext and IDbSet do everything you need and include the \"Unit Of Work\" inside DbContext. Am I missing something here or does it seem people enjoy adding another layer of dependency for no reason. 回答1: You are actually right. DbContext is an implementation of the unit of work pattern and IDbSet