I worked around this by adding a sub-dependency resolver wich resolves IEnumerable<TSomething> from a container in the normal way (to do so I was to pass the container into the constructor of the resolver).
On 20 июн, 02:36, Vadimmer <[email protected]> wrote: > I would like to register IEnumerable<TSomething> in a container and > then resolve it as IEnumerable<TSomething>. > At the moment Windsor prevents me from doing so as it considers > IEnumerable<TSomething> constructor argument is a parameter and not a > service. I perfectly see the root is in the GenericListConvertor. Is > there any way to turn it off for a particular registration? > > P.S. As a workaround I had to introduce ISomethingSequence and > register the component implementing this contract. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
