I would like to bring this to your attention, that the behavior you’re describing was actually a bug, and it is fixed in current version (v2.1)
Since your post is pretty high in search engines, I think it might beneficial to put a notification about it on top of the post, to avoid confusing people seeking information about how that works in current version.

In our code at work, that’s not a problem because we never resolve the IUnitOfWork directly, and it’s always used as a dependency of a resolved component (a Request Handler). That resolved component is always released through the container.

You can also avoid the problem like this:
http://davybrion.com/blog/2008/12/the-resolvable/

From this post, it seems that whenever I use Container.Resolve() on a type that implements IDisposable, then I should not use the returned instance in a using statement, but rather wrap it in a try-catch-finally block so I always call Container.Release ?

But in your post about managing NHibernate sessions (http://davybrion.com/blog/2008/06/managing-your-nhibernate-sessions/) you have the following code:

public ProductCategoryDTO[] GetAllProductCategories()
{
using (Container.Resolve())
{
var repository = Container.Resolve();
var categories = repository.GetAllProductCategories();
return categories.ToDTOs();
}
}

Now my question is this: is this not “wrong” according the information of this post? Doesn’t this mean that the IUnitOfWork instance will never be released from the container since it implements IDispoable?

If so, how would you handle this properly?

Thanks in advance,
Morten Jacobsen


public interface IMyComponent { }

[TestMethod]
public void ContainerDoesntKeepReferenceToNotDisposableComponent()
{
var container = CreateContainer();
var myComponent = container.Resolve();
Assert.IsFalse(container.Kernel.ReleasePolicy.HasTrack(myComponent));
}



var container = new WindsorContainer();

container.Register(... // <---- I have no register method.