Firstly, I am impressed for your work. It's great. I use the repository pattern on a daily basis, but often it seems to me that this is the abstraction of the abstract. What do you think about this article?
<a class="postlink" href="http://rob.conery.io/2014/03/04/repositories-and-unitofwork-are-not-a-good-idea/">http://rob.conery.io/2014/03/04/reposit ... good-idea/</a>
1 Answer(s)
-
0
Hi,
I answered a similar question before: <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/issues/525#issuecomment-134895043">https://github.com/aspnetboilerplate/as ... -134895043</a>
I also did read the article before. First of all, ABP's Repository and UnitOfWork implementation is very different than the article describes. Repository is a known pattern and widely used. At least it abstracts EntityFramework from our application, creates a data store abstraction, allows unit tests to be simpler and so on. I think it's better than working directly from DbContext.
