Hi Stefan, Thanks for the info! Had not realise this.
Knave On Jan 30, 3:36 pm, Stefan Sedich <[email protected]> wrote: > Make sure the registration is set as transient if using XML add > lifestyle="transient" should do the trick. > > By default Windsor returns singleton instances unless you specify a > transient life cycle. > > Cheers > > Stefan Sedich > > On 30/01/2009, at 5:08 PM, KnaveT <[email protected]> wrote: > > > > > Hi all, > > > I am using Windsor 1.0.3.5363 and is experiencing a problem. > > > I have an interface, e.g. IRenderingService and a provider > > RenderingServiceProvider that inherits this interface. Now everything > > works fine. Windsor resolves the correct class and it just works. > > > until I discover that windsor is returning an "old" object. The 2nd > > time I call IoC.Resolve< IRenderingService>(), it will not create a > > new instance. Instead it returns the object that was resolved the 1st > > time its loaded. > > > I tried putting breakpoints etc. No use. Debugger shows the old object > > is returned from windsor (old data were populated in the returned > > object). > > > I wonder if I had configured wrongly? > > > Thanks. > > Knave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
