Thanks for the links...will check them out. However am attaching a comment I left on Ayende's "Open Source Project Maturity Model" ( http://ayende.com/Blog/archive/2009/02/12/ayendes-open-source-project-maturity-model.aspx )
I would like to adress the stackoverflow comment...while stackoverlow is > very cool it does add "one more place to look. With any software product > there should be a single authoritative source for anwers. If an answer > cannot be found through this source the net should then be cast wider. I see > RhinoMocks questions pop up on stackoverflow and other sites and wonder why > the person asked the question there rather than, to me, the most obvious > place. (Probably has to due with points or badges or some other metric not > awarded on a mailing list) > > It probably should be said here that I myself am quite active on the Rhino > mailing list and am quite partieal to the help that myself and the other > dedicated mailing list members supply. > Tim On Fri, Feb 27, 2009 at 12:38 PM, Germán Schuager <[email protected]>wrote: > > http://stackoverflow.com/questions/197274/what-are-forwardedtypes-in-the-context-of-castle-windsor-component-registration > > http://stackoverflow.com/questions/274220/does-castle-windsor-support-forwardedtypes-via-xml-configuration > > > > On Fri, Feb 27, 2009 at 3:17 PM, Tuna Toksoz <[email protected]> wrote: > >> I remember there was a method "ForwardTo", i was the thing IIRC >> Tuna Toksöz >> http://tunatoksoz.com >> http://turkiyealt.net >> http://twitter.com/tehlike >> >> Typos included to enhance the readers attention! >> >> >> >> >> On Fri, Feb 27, 2009 at 7:17 PM, Bill Barry <[email protected]>wrote: >> >>> I don't know how it can be done with the xml configuration, but you can >>> do it with fluent registration (something like this): >>> >>> Container.Register(Component.For<IThinInterface2>().Instance((IThinInterface2)Container.Resolve<IThinInterface1>()) >>> >>> >>> Tim Barcz wrote: >>> >>> public class MyConcreteClass : IThinInterface1, IThinInterface2 >>> { >>> .... >>> } >>> >>> Can I do this with one registration or do I need two? >>> >>> In and Ideal World (possible???): >>> >>> <component id="Component1" >>> service="MyAssembly.IThinInterface1, Assembly" >>> service="MyAssembly.IThinInterface2, Assembly" >>> type="MyAssembly.MyConcreteClass Assembly" /> >>> >>> How it's done right now? >>> >>> <component id="Component1" >>> service="MyAssembly.IThinInterface1, Assembly" >>> type="MyAssembly.MyConcreteClass Assembly" /> >>> >>> >>> <component id="Component2" >>> service="MyAssembly.IThinInterface2, Assembly" >>> type="MyAssembly.MyConcreteClass Assembly" /> >>> >>> >>> The issue if I want a singleton instance but the component registration >>> is backed by the same concrete class I would think that class would get >>> created twice. Thoughts? Recommendations? >>> >>> Tim >>> >>> >>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
