Well, you could always send a patch for this ;-) However, I'd try to wrap the 3rd party lib (with adapters/ factories)... it will be ultimately cleaner. Unless you have to write *lots* of wrappers.
Also remember this thread: http://groups.google.com/group/castle-project-devel/browse_thread/thread/43aa513817bd057a/553d069ff3352656 On May 18, 1:18 am, George Mauer <[email protected]> wrote: > Thanks Mauricio, I had actually forgotten about that post but I was > hoping that something got introduced into the trunk to do this so I > wouldn't have to roll my own. > > On May 17, 11:10 pm, Mauricio Scheffer <[email protected]> > wrote: > > > > > You already asked that a few months ago at > > stackoverflow...http://stackoverflow.com/questions/178611/ > > Didn't that work out? > > > On May 18, 12:41 am, George Mauer <[email protected]> wrote: > > > > I would like to specify that my container should not resolve property/ > > > optional dependencies. > > > > I do not have control over the library in question so I cannot add a > > > DoNotWire attribute to properties, instead I would like to specify > > > this from the container registration (preferably in the fluent > > > registration). > > > > Can I do this on a per-component basis? Can I just specify that I > > > don't want any of the optional dependencies in the container 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 -~----------~----~----~----~------~----~------~--~---
