We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are legitimate cases for having bindings that differ by Implementation Type (relying on duplicate Service Types):
However, these cause Duplicate Key Exceptions when registering singletons in WrappedServiceProvider:
https://github.com/smudge202/compose/blob/dev/src/Compose/WrappedServiceProvider.cs#L17
The text was updated successfully, but these errors were encountered:
Likely caused by this: smudge202@3605ffe
Sorry, something went wrong.
As per https://github.com/aspnet/Options/blob/dev/src/Microsoft.Framework.OptionsModel/OptionsManager.cs#L37 the options model is designed as an aggregation/additive configuration model. We're hitting this issue increasingly frequently at 4Com.
Fixed #61 but caused regression
01307bc
This has been resolved as part of the structural change found here: 4Com/compose#1
smudge202
Successfully merging a pull request may close this issue.
There are legitimate cases for having bindings that differ by Implementation Type (relying on duplicate Service Types):
However, these cause Duplicate Key Exceptions when registering singletons in WrappedServiceProvider:
https://github.com/smudge202/compose/blob/dev/src/Compose/WrappedServiceProvider.cs#L17
The text was updated successfully, but these errors were encountered: