Hi Mauricio, Thanks for your help. I did run the test you proposed and it works the way it's supposed. The compoenent gets registered as Singleton and acts as such.
Still I can't find the bug in my code. I traced it step by step only to find that, upon each invocation of "container.Resolve<..." a new instance is built. I also tried to specify its singleton nature upon registration, still no luck. The container I build gets passed to various components belonging to different assemblies. Each of those components ask for an instance of the Application Facade I register at application launch time. To me this seems like a pretty simple situation and I don't expect such a kind of misbehaviour to happen. /me clueless. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
