-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
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
Microsoft.Extensions.Options and child container - failing test case #43
Comments
Any updates on this one? |
I'm not really sure what to do about this one? I don't really know SM well enough to say what the issue might be or how to fix it. |
That makes two of us ;-) |
It seems structuremap is no longer actively supported, and the replacement is Lamar: https://jasperfx.github.io/lamar/documentation/ioc/ I'll close this issue for now, i'll probably end up dropping support for structuremap completely, and tryijng out lamar at some point down the road. |
I can't use Lamar because Lamar doesnt support (or intend to support) child containers - which is something I'm dependent upon in order to model system wide, and per tenant wide services in a multitenant platform. |
Hello,
I have put together a couple of test cases to show this issue. I'm seeing some funny behaviour when attempting to use
Microsoft.Extensions.Options;
.This first test case shows adding Options to a root level container, then resolving them, and it passes:
That's fine so far. The problem comes when I try and configure this at
child
container level.Here is the failing test case:
This latter test case, the delegate to configure the option
b.Prop = true;
is never called.I'm not very advanced with structuremap, would appreciate any guidance etc.
Thanks
The text was updated successfully, but these errors were encountered: