You can register a release policy that just ignores this. On Fri, Oct 24, 2008 at 12:56 PM, codemonkey <[EMAIL PROTECTED]>wrote:
> > Hello, > > I have seen this post > http://stackoverflow.com/questions/132940/why-does-castle-windsor-hold-onto-transient-objects > , > it is quite interesting something that might bite me hard. What is the > best practices for handling this with Windsor? > > Any tips for ensuring I don't have any leaks in my asp.net app. I have > 1 container which is cached for my app lifecycle. And at the moment I > am resolving say a transient Presenter which is injected various > services etc with constructor injection. At the moment I do not > release anything. > > > Cheers > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
