Untill now I have been suing a quite awkward way of communicating between my Program (Stadard EXE) and a plugin (ActiveX DLL). I't not a good way I am currenctly using and I want to make it better.

Recently I studied how to make plugins for VB etc.
It seems you can create a VBIDE object and then use many various functions, properties etc. etc. through that plugin.

I can do that too in my Plugin system but it's only one-way communication and only "first level".

Fx. I want the plugin to be able to bind an object, say "MainProgramObjectThingie" to the Standard EXE (does it help if it's a ActiveX EXE?) and thereby be able to issue commands like...

MainProgramObjectThingie.Menus.Add "Test plugin"
MainProgramObjectThingie.GetCurrentFileName

...and so on

As for now it only works the other way around. The main program can call the Plugin and issue commands like

PluginObjecjThingie.ShowAboutBox

I would like to have it work in both directions so that I don't have to use the SendMessage API each time the plugin will send information to the Main Program.

HELP ANYONE?!?