why do you have the properties settable if you don't want to set them? 2010/4/12 jorge.rowies <[email protected]>: > Hello, Roelof Blom said in the last post of this thread: > > http://groups.google.com/group/castle-project-users/browse_thread/thread/ca840efccd73476d/a97f3379b9649bcc?lnk=gst&q=auto+wiring#a97f3379b9649bcc > > That one way of disabling property auto-wiring could be achieved with > something like this: > > container.Register(Component > .For(impl) .LifeStyle.Transient) > .Activator<MyModelActivator>() > > class MyModelActivator: DefaultComponentActivator > { > protected override void SetUpProperties(object instance, > CreationContext > context) > { > // Do not auto-wire > } > > } > > Which worked great for me, but now I am having problems using > ServiceOverrides to set dependencies on a property, and I think it is > because of this custom activator. > > Is there any way to prevent property auto wiring and still be able to > use ServiceOverrides? > > Thanks a lot > > -- > 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. > >
-- 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.
