Castle Windsor VS DryIoc

Most of the DI containers have a feature of resolving components by name. Here's an example of a "typed factory" that can be provided by the container and the component name can be used to select the service implementation: https://github.com/castleproject/Windsor/blob/master/docs/typed-factory-facility-interface-based.md

I'd like to keep the convention-based assembly scanning capabilities if ever that was possible. It's too convenient and less error prone than manually registering everything through attributes like current source generator strategies go. DryIocZero supports this somewhat using t4 templates, it gives you a method where you can register your stuff and do assembly scanning and it'll generate your container from there. It works and is quite small and fast but the UX does need some work since t4 is rather clunky to write on.