Two issues:
- First, it doesn't always get picked up apparently because we sometimes ask for the service without passing the invariant name as a key. I'm not sure why this is, but it seems like a bug. So far I have only see this happen when using the initializer path for checking model compat.
- Second, there is a two-stage resolve process where we ask for a factory using the invariant name as a key first, and then ask again for a "default" if no factory with a key is found. But there is no sugar method on DbConfiguration for registering a factory without a key.
- First, it doesn't always get picked up apparently because we sometimes ask for the service without passing the invariant name as a key. I'm not sure why this is, but it seems like a bug. So far I have only see this happen when using the initializer path for checking model compat.
- Second, there is a two-stage resolve process where we ask for a factory using the invariant name as a key first, and then ask again for a "default" if no factory with a key is found. But there is no sugar method on DbConfiguration for registering a factory without a key.