Harness IModule for purpose like NinjectModule ?

[sigmarsson]

Perhaps this idea would be just an inappropriate use but probably reusing an IoC configuration in terms of type registration can be a frequent demand while setting up and launching unit tests. (I read somewhere that Prism has stopped fusioning with Ninject due to its limitation on the mobile platforms)

Earlier I used this class to share the IoC setups among the application and different unit tests:

I currently have 2 IModule classes;

• 1. for the views, regions and dialogs i.e. one for the overall UI
• 2. another is for the unit tests i.e. a headless one (currently this is IoCSetup above)

and later merge them in the ConfigureModuleCatalog;

Is it something you could advise to follow through to substitue NinjectModules and inherit the unit test classes from PrismApplication as a legitim solution ?

[sigmarsson]

• HeadlessIocSetup : IModule
• HeadIocSetup : IModule

Could I reuse the first IModule class in my Unit Tests so that all service registrations would be available as they are in the PrismApplication ?