Unit Testing on Top of Entity Framework DbContext
When writing unit tests one of the challenges is to isolate your tests from everything. To isolate them from the code that is not in their
Repository Implementations
In my previous post I have presented a way to separate your data access from the business logic, when a relational database is used. I have
Separating Data Access Concern
In our days most of the applications that have a relational database as storage, use an ORM to access the data. The ORM (Entity Framework, Hibernate,
Who Disposes Your Repository
Recently, I’ve went again through the discussion of how the Repository Pattern works with Dependency Injection (DI) in one of the projects I’m involved
I'm a speaker at
Founder and Partner
Partner
Recent posts
- Why Programmers Should Challenge the Stakeholders
- Migrate to Ghost 1.x on Azure
- Decide between In-Process or Inter-Process Communication at Deploy Time - Part 3
- Decide between In-Process or Inter-Process Communication at Deploy Time - Part 2
- Decide between In-Process or Inter-Process Communication at Deploy Time