Can you both please try
container.ReleasePolicy = new Releasers.AllComponentsReleasePolicy();



Tuna Toksöz
Eternal sunshine of the open source mind.

http://devlicio.us/blogs/tuna_toksoz
http://tunatoksoz.com
http://twitter.com/tehlike




On Tue, Sep 8, 2009 at 8:57 AM, tom <[email protected]> wrote:

>
> I had a problem with it not releasing instances, and I got the latest
> and compiled and it took care of the problem.  This was just last
> week.  I really don't know if anything was changed, but for some
> reason it took care of the problem.  Just thought I would throw that
> out there.
>
> On Sep 8, 6:07 am, SimoneB <[email protected]> wrote:
> > Looking at the code of PerWebRequest related classes, I thought that
> > the components resolved are automatically released. Not sure though.
> >
> > On Sep 8, 10:34 am, Ken Egozi <[email protected]> wrote:
> >
> > > I *think* that whenever you explicitly Resolve, you have to explicitly
> > > Release.Dependencies resolved by windsor will get released when they
> aren't
> > > needed any more.
> >
> > > On Tue, Sep 8, 2009 at 9:47 AM, SimoneB <[email protected]>
> wrote:
> >
> > > > Hi there,
> >
> > > > I'm having some issues with managing release of components in a web
> > > > application built on ASP.NET WebForms. I set up a MVC pattern where
> at
> > > > the beginning of the request I inject my controllers into the pages.
> > > > The controllers are registered with PerWebRequest lifestyle, and as I
> > > > see from the code they are supposed to be released by the container
> > > > when the request ends. They have several dependencies with mixed
> > > > lifestyles, and usign a profiler I notice that many of them are not
> > > > actually released, instead at each request the number of instances
> > > > grows up.
> >
> > > > I'm pretty sure I'm doing something wrong so I wanted a heads up to
> > > > what to look for to investigate this issue. The controllers - which
> > > > are the only one I resolve explicitly from the container - depend on
> > > > several other components with mixed lifestyles some of which
> implement
> > > > the IDisposable interface - which I know caused issues in the past
> due
> > > > to a problem about component burden which afaik should be fixed now.
> > > > Is there anything specific I should be looking for to investigate
> this
> > > > issue?
> >
> > > > Thanks
> >
> > > --
> > > Ken Egozi.
> http://www.kenegozi.com/bloghttp://www.delver.comhttp://www.musicglue...הכנס
> הקהילתי הראשון למפתחי דוטנט - בואו בהמוניכם
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to