Actually Binsor does support it component Impl < Interface, Interface2,...,interfaceN
https://rhino-tools.svn.sourceforge.net/svnroot/rhino-tools/trunk/rhino-commons/Rhino.Commons.Test/Binsor/ComponentForwarding.boo On Mon, Jan 5, 2009 at 4:16 PM, Ayende Rahien <[email protected]> wrote: > Binsor doesn't support this currently. > > Binsor seems more flexible at times, especially with regards to production > time editing. > But I am using C# FI a lot these days > > > On Tue, Jan 6, 2009 at 12:06 AM, Robert M. <[email protected]>wrote: > >> >> Is there any support in Binsor for it? It seems to be available only >> in C# fluent interface. >> >> By the way, now that fluent interface in C# for Windsor is available, >> would you see a big advantage in further usage of Binsor for >> configuration? >> >> On Jan 5, 11:55 pm, "Ayende Rahien" <[email protected]> wrote: >> > Forward<T> >> > >> > On Mon, Jan 5, 2009 at 11:52 PM, Robert M. <[email protected]> >> wrote: >> > >> > > I have a class which implements two interfaces. I've registered a >> > > component with Windsor with the first interface. >> > > Resolve<IFirstInterface> provides me the proper object for the >> > > specified interface. How should I register the component so that when >> > > I request Resolve<ISecondInterface>, Windsor to respond with the same >> > > instance of the class? >> > >> > > Thanks! >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
