Do not abstract/hijack the IoC container registration

[kkozmic]

One friction point encountered with frameworks that abstract registration into the container, like Nimbus does right now, is that this often makes it really hard to deal with some more advanced scenarios like customise how a particular handler is registered, or test the registration (a convention test).

Are there any plans to explore alternative ways of integrating with a container, to make it more flexible?

[uglybugger]

Definitely.

We'd love to hear if you have any ideas about how to make it more friendly - bootstrapping is something we've put a fair bit of thought into and recognise that it's still far from perfect.

For what it's worth, the infrastructure contracts are put together in a way that allows for custom handler registrations etc. but the sticking point then becomes the container-specific message brokers themselves. You can register your handlers and brokers yourself (just don't call the container-specific .WithXXXDefaults(...) extension method) but that's something that still needs tidying up.

[kkozmic]

Ok, I'll try spiking a pull request to put the ideas in my head into practice, and we'll see where it takes us

[uglybugger]

Hey.. Did you get anywhere with this one?

[kkozmic]

Haven't touched it :)

Perhaps a good task for a hackatron