Closed mscrivo closed 7 years ago
Turns out the way you need to register it is different from Ninject, unsure whether that's a bug or by design. See here for solution: https://stackoverflow.com/questions/44725490/simpleinjector-and-microsoft-webhook-asp-net-webhooks/44729307#44729307
We have a Stripe Webhook handler implementation that is working perfectly with Ninject. Recently we did a migration from Ninject to SimpleInjector and, while everything else went well, we cannot get this webhook handler to work anymore. Here is the error:
You'll notice that the SimpleInjector.Integration.WebApi.SimpleInjectorWebApiDependencyResolver is correctly hooked up to the IDependencyScope, but for some reason it's still trying to create it's own instance of our webhook handler with a parameterless constructor. Our implementation only has 1 constructor with 2 dependencies.
Anyhow know what's going on here?