Disposable Instances Series
In the past few weeks I have published a set of four posts that deal with disposable instances. These posts describe in detail a working implementation
Disposing Instances when Using Inversion of Control
In the last few posts I have written about how to deal with IDisposable instances when using Dependency Injection. In the Who Disposes Your Repository I
Extending Unity Container for IDisposable Instances (2nd approach)
In my previous blog post I detailed an approach of making the Unity Dependency Injection Container ț̦o automatically call Dispose() on all the IDisposable instances
Extending Unity Container for IDisposable Instances (1st approach)
A few weeks ago, in my blog post ‘Who Disposes Your Repository’ I wrote about the challenges of implementing an IDisposable repository, which takes full advantage
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
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