I’ve often found it interesting that the Microsoft Dependency Injection package doesn’t offer a way to register all implementations of a type out the box. This tends to be standard with other DI providers to save on developer friction (having to add the implementation to your container every time you add a new implementation).
Recently I’ve been using Scientist to test critical path changes within a codebase. The library is amazing, but one thing I found a bit cumbersome was getting the dependencies in place for the Try method. I often wanted to use interfaces for the experiment that were already being used and registered by the main application. To plug this hole, I created a library, Scientist.DependencyInjection