Asked (and answered) on stackoverflow: http://stackoverflow.com/questions/6574584/how-do-i-tell-windsor-to-error-if-it-cant- resolve-a-property
I added a link to the workaround you want, but I still recommend a proper refactor instead of trying to work around symptoms... -- Mauricio On Mon, Jul 4, 2011 at 4:21 PM, Matthew Shapiro <[email protected]> wrote: > I am trying to utilize property injection in a "safe" way, and what I > mean by that is I want Windsor to exception if it can't resolve a > property. If it silently fails and just leaves the property as null > (as it is now), it will not be immediately noticable that IoC is > failing for a type, and can cause hidden errors that will take some > time to debug (and be hard to unit test for). > > Is there any attribute I can add to a property to tell Windsor to try > and resolve a property, and if it can't then throw an exception with > the same exception that it would throw if a constructor dependency > couldn't be resolved? > > -- > 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.
