They are just a bit more dynamic than an anonymous object or a dictionary
passed into DynamicParameters.
Wouldn't it work to run that delegate at resolve time to update
CurrentState? Of course, with some sort of indicator to explicitly advise
the container to do this, else it would probably
yup, the factory method will get you there for now, and I'm happy to have a
look at more constrained version of dynamic parameters for future release
--
Krzysztof Kozmic
On Tuesday, 19 February 2013 at 8:13 PM, bhaal...@gmail.com wrote:
They are just a bit more dynamic than an anonymous
Dang, my colleague just linked me to
http://issues.castleproject.org/issue/IOC-367 which seems to be exactly my
problem - the real application does exactly that (having a WCF Service
which doesn't want to start).
--
You received this message because you are subscribed to the Google Groups
Yeah, since dynamic parameters are just that - dynamic, WIndsor has no way to
statically determine which parameters will be provided.
The workaround for now is to make the property mandatory when registering Foo
HTH
--
Krzysztof Kozmic
On Tuesday, 19 February 2013 at 12:03 AM,
