I see your point, and while it is definitely a repository pattern already, I find that due to the dependency inversion principle, it's too concrete just to go direct to EF. I do all of my testing with
a mocking container, making use of IoC for do dependency injection, which is simple with IRepository<T>. Doing it this way also gives a clear path to using an IoC container in live code too.
↧