I tried posting this before, didn't seem to work. Sorry if you got it
twice.
It's in response to
http://groups.google.com/group/castle-project-users/browse_thread/thread/831d5862dccf13e2/4bd4dbaa051f7089?lnk=gstq=IEnumerable#4bd4dbaa051f7089
I have the same problem. Here is a test to show the
Yes, like the linked thread you can use a sub dependency resolver. There are
2 baked into MicroKernel (for arrays and lists, however an IEnumerableT
should be just as easy).
You register it as follows:
Kernel.Resolver.AddSubResolver(new ArrayResolver(Kernel));
If you can use an array instead of an IEnumerable, then you only need
to add the ArrayResolver: http://stackoverflow.com/questions/1057977
On Oct 12, 6:21 am, Thejuan aamills...@gmail.com wrote:
I tried posting this before, didn't seem to work. Sorry if you got it
twice.
It's in response
Can you show the problematic code?
On Fri, Jun 19, 2009 at 11:36 PM, Vadimmer vadimkanto...@gmail.com wrote:
I would like to register IEnumerableTSomething in a container and
then resolve it as IEnumerableTSomething.
At the moment Windsor prevents me from doing so as it considers
IEnumerableTSomething in a container and
then resolve it as IEnumerableTSomething.
At the moment Windsor prevents me from doing so as it considers
IEnumerableTSomething constructor argument is a parameter and not a
service. I perfectly see the root is in the GenericListConvertor. Is
there any way
I would like to register IEnumerableTSomething in a container and
then resolve it as IEnumerableTSomething.
At the moment Windsor prevents me from doing so as it considers
IEnumerableTSomething constructor argument is a parameter and not a
service. I perfectly see the root
