Home/ Questions/Q 8502747
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T01:34:18+00:00

I have read almost all articles about Repository pattern and different implementations of it.

  • 0

I have read almost all articles about Repository pattern and different implementations of it. Many of them judged bad practices (ex: using IQueryable<T> instead of IList<T>) etc. that why i’m still stuck and couldn’t end-up to the right one.

So:

  • Do I need Repository pattern to apply IoC in my MVVM applications ?

  • If yes, What is the efficient IRepository implementation to EF Entities which is a good practice and better testable ?

  • How can I test my Repositories and UnitofWork behavior ? Unit tests against in memory Repositories ? Integration tests ?

Edit : According to answers I added the first question.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Ayende Rahien has a lot of posts about repository http://ayende.com/blog/search?q=repository and why it is bad when you are using ORM’s. I thought Repository was the way to go. Maybe it was, in 2004. Not now. ORM’s already implement repository. In case of EF it is IDbSet. And DbContext is UnitOfWork. Creating a repository to wrap EF or other ORM’s adds a lot of unnecessary complexity.

    Do integration testing of code that will interact with database.

    • 0