I'm trying to avoid coupling the assembly to Castle - and I don't want to remove the PropertyInspector from the kernel as there may be other components that do need the property resolution.
What I've done temporarily is to clear the component's Properties collection after registration - I'll see if I can improve on that a bit later but I'm not sure that the IRegistration object has sufficient behaviour to avoid registering the properties. On Apr 9, 4:15 pm, Victor Kornov <[email protected]> wrote: > There is also [DoNotWire] attrib in Castle.Core > > > > On Thu, Apr 9, 2009 at 5:29 PM, Paul Hatcher <[email protected]> wrote: > > > Is there a way of telling Castle not to wire up properties via the > > fluent interface, i.e. to just do constructor injection?- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
