Using this with already present StructureMap container?
See original GitHub issueHi,
So, I’m trying to migrate to this from SaasKit because this seems more what I want.
I have followed the samples for StructureMap and TenantContainers, but I end up with an error:
No default Instance is registered and cannot be automatically determined for type 'ITenantContainerBuilder<AppTenant>'
AppTenant
is my tenant class and I have this in Startup:
https://gist.github.com/knepe/1bd885d1764b533356c7c133022e39a4
Any clue of what I’m doing wrong? I want to use StructureMap for the “generic services” as I use stuff like Scan and Decorate
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Getting Reference to StructureMap Container
I'm new to StructureMap and have a scenario where I would like to get a handle to the container. ... IContainer container =...
Read more >Using the Container Model
Model represents a static view of what a Container already has, and does not account for policies that may allow StructureMap to validly...
Read more >Changing Configuration at Runtime
If you need to add or change configuration to an existing StructureMap Container object, you can use the IContainer.Configure() method to add or...
Read more >A Gentle Quickstart
Configure the container by registering the what and how StructureMap should build or find requested services based on a type and/or name. Resolve...
Read more >StructureMap
StructureMap is a feature rich IoC tool with support for interception, object lifecycles and intelligent disposal patterns, open generic types, modular ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Glad to hear you made progress! I don’t think it would be too much work to allow passing in an existing root container… i’ll leave this open to track this.
I am going to close this, because I am deciding to deprecate structuremap in favour of lamar. There have been issues with structuremap that prevent stuff working with child containers correctly, and the feedback when these were raised: https://github.com/structuremap/structuremap/issues/618 was basically that structuremap is no longer actively supported, and to switch to lamar. This makes it a bad choice for me to use moving forwards.