IoC Module Reuse

[sigmarsson]

Hi,

Is it possible to reuse a pre-configured IoC module in Stylet's bootstrapper ?

protected override void ConfigureIoC(IStyletIoCBuilder builder);

NInject and DryIoc both maintains aspiration to keep configurations in a dedicated module, those modules facilitate unit testing as well.

NInject

public class MyIoCSetup : NinjectModule
{
  public override void Load()
  {
     // ... Perform bindings here. 
  }
}

DryIoC

dadhi/DryIoc#326

[canton7]

https://github.com/canton7/Stylet/wiki/StyletIoC-Modules ?

[sigmarsson]

That is cool. Do you think it would be possible to standardize these modules across the globe by having a IIoCModule interface or alike?

Basically, the mapping might be very similar duty for all IoC containers. I am asking all this because you earlier stipulated that you are not keen on delivering a separate nuget package for a stand alone Stylet IoC. I have a configuration set up for a different infrastructure now with NInject and wish transfer and apply that config. DryIoC will offer this soon perhaps with the next feat release. Do you see a chance to fusion with others on any degree on this matter ? Thanks !

[canton7]

I don't follow I'm afraid. Every ioc container has a different interface for registering types with it. That Bind call in StyletIoCModule is only the start: there are a ton of other methods you call on the IBindTo which is returned.

If there's ever going to be standardisation, it will probably be everyone moving to Microsoft.Extensions.DependencyInjection.

If you've already got infrastructure set up with Ninject, then just use the NinjectBootstrapper and drop StyletIoC entirely.