Use other dependency injection framework

How can I use your WorkflowCore with a different dependency injection framework? I tried to add an extension method similar to the one you have in ServiceCollectionExtensions, but I noticed that WorkflowOptions depends on IServiceCollection. Can I somehow register workflow options with a different DI container?

Thanks

[danielgerlag]

Yeah, I don’t agree with the blog by the Simple injector guy… very much an opinion. There is a bridge for Microsoft.Extensions.DependencyInjection.Abstractions and simpleInjector… but Simple Injector is also finicky about mixing components with different lifetime scopes… not my favorite IoC container… if the basic IoC you get out of the box with .Net Core is not enough… look into Autofac.

[Kahbazi]

WorkflowCore depends on Microsoft.Extensions.DependencyInjection.Abstractions and simpleInjector will not have an implementation for it, here’s the reason why. https://simpleinjector.org/blog/2016/06/whats-wrong-with-the-asp-net-core-di-abstraction/

And the integration of simpleinjector and AspNetCore is that you register your application services to simpleinjector container and simpleinjector would resolve MVC Controllers and and all the other services that are registered by Microsoft container (ex workflowCore, all the Microsoft.Extensions packages) is resolved by microsoft container, through simpleInjector Crosswire. So even if you follow the integration simpleInjector would do nothing for resolving workflowCore services.

So the only way that you can get workflowCore from simpleInjector is what @eddie3716 suggested.