In a previous post I discuss about the importance of calling IWindsorContainer.Release() for all object created through Windsor, to avoid memory leak. There is a little correction to do, the container keeps a reference to an object created through Resolve<T> only if that object implements IDisposable. But it is important to really understand the concept [...]
Continue reading about Castle.Windsor and lifecycle of objects
The WindsorContainer has a method call release that must be called to release the instance of transient object that gets created by the container itself. If you forget to call release, the container keeps a reference to all transient object created with resolve, that prevent the garbage collector from reclaiming the memory of that object. [...]
Continue reading about The importance of WindsorContainer.Release()
This morning I turn on a virtual machine, and when I try to change configuration a strange error (Vmdb error -2: Schema path not found ) appears. After a little search I discover that my server version is version 1.0.3 and the console is 1.0.2. The error turns out to be caused by the installer [...]
Continue reading about VmWare update installer ( Vmdb error -2: Schema path not found )
Thanks to my friend Janky for notice that I made a mistake in a previous post. In that post I speak about a “conversation” but actually I was describing a UnitOfWork, that was my fault. The exact definition of a conversation is given in “Hibernate In Action” where Gavin King states that.
“We call a unit [...]
When you use a generic Interface for repository pattern there is always the problem of Query object. If you use nhibernate you can use Criteria API, but if you want to make your code not dependent by the ORM used, you often need to implement your Criteria Query. The most annoying problem with this approach [...]
