Reputation: 1173
This should be an easy one,
I have a DomainModule
and a ServicesModule
where DomainModule
uses ServicesModule
.
DomainModule --> ServicesModule
Module's definitions :
[ModuleDependency("ServicesModule")]
[Module(ModuleName = "DomainModule")]
public class DomainModule : ModuleBase
...
[Module(ModuleName = "ServicesModule")]
public class ServicesModule : ModuleBase
The error I'm getting :
A module declared a dependency on another module which is not declared to be loaded. Missing module(s): ServicesModule
Not sure that if I add a reference to the ServicesModule
will I lose the loose coupling rule or not, but I tried not to do that, If I'm wrong on this tell me please.
What is your suggestions/hints on this ?
Upvotes: 0
Views: 1584
Reputation: 81313
The current release of the Composite Application Library do not bring support for loading modules on demand with dependencies.
But there is a workaround to this by creating an extension method to load the dependent modules
which can be found here.
Upvotes: 1