Kristian Hellang

Something leads me to believe that this is a StructureMap bug related to `TryGetInstance` and open generics. The open generic registration is there all along, but it won't "materialize" until...

Haha. Right. I think we're getting somewhere... Now we just need to figure out what we can do about this. I'm afraid this will get very hairy.

Hmm. I'll have a look. It sounds really weird that a singleton should be disposed when a nested container is disposed.

Translation (courtesy of Google Translate): > Failed to load file or assembly "System.Net.Http, Version = 4.0.0.0, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a" or one of its dependencies. The assembly list...

I'm not sure how this is related to StructureMap.Microsoft.DependencyInjection? 🤔

Hmm. That's weird. I thought we would only pick constructors we could satisfy. Why is `IActionContextAccessor` used, but not registered is another question.

We'll gladly accept a PR to support ASP.NET Core 3

@dustinsoftware The library already provides a `StructureMapServiceProviderFactory`, (but it works with `Registry`, not `Container`), so you don't have to write that yourself. The only thing you should have to do,...

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.

What makes you think this is related to StructureMap.Microsoft.DependencyInjection? This looks like an issue with StructureMap itself.