I am writing a custom module for which IMC seemed a perfect fit.  It doesn't work.

I have a single module with three user controls.  In my module definition I have three definitions, all with blank keys, one for each control so that when the module is placed on the page all three controls show up.

I wanted one control to implement IModuleCommunicator so that it could talk to the other two which implement IModuleListener.

I am finding that the two controls implementing IModuleListener never receive any calls.  If I make the communicator control ALSO a listener then it gets it's own events.  I found another thread where a developer seems to have the same problem as I do. (http://kemmis.info/blog/archive/2008/02/22/dotnetnuke-inter-module-communication-or-how-your-modules-can-get-their.aspx scroll a looong way down for the comment by Nick Chance).  I do not have a DNN4 install to test this on ATM so I cannot confirm that the code was broken by V5.

Have I misunderstood how this is meant to work?  Is there a better way to communicate between the differnent contorls of a module?

Dave,

Many thanks. 

My Google (lack of) skills failed to turn up any of those resources.

Hi,

I'm also having the same problem in dnn 5.1.x with IMC. I googled it a lot and no actual solution out there, neither in GEMINI.
The reason could be is that, the receiver did not initialize the IModuleListener OnModuleCommunication event correctly.
So the sender can't raise the event.

 Any help will be greatly appreciated.

thanks