Agreed, this isn't relevant to a specific ioc. I'm using Rhino.Commons IoC static accessor to reach the IWindsorContainer instance. I don't think it's necessary for NH to build anything into the framework in order to reach the container. It's up to the user to provide their own mechanism in their own tuplizer/instantiator.
2008/11/20 Ken Egozi <[EMAIL PROTECTED]> > but does it make any difference for implementing Lee's feature (and one > that I like to have myself - letting the IoC instantiate persisted > entities)? the implementation should be almost similar for any reasonable > IoC, as the usage (in terms of resolving an instance) is almost identical > across > > On Thu, Nov 20, 2008 at 4:47 PM, Fabio Maulo <[EMAIL PROTECTED]> wrote: > >> The second questions was for Ken.Understand: You are using >> Castle.Windsor. I'm a Windsor user too (so far), but a lot of my customers >> are using Spring.Net. >> For me it is not so logical that who are using NH mean that they are using >> Castle.Windsor. >> >> -- >> Fabio Maulo >> >> >> > > > -- > Ken Egozi. > http://www.kenegozi.com/blog > http://www.delver.com > http://www.musicglue.com > http://www.castleproject.org > http://www.gotfriends.co.il > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
