Allen,

I have 2 Components / assemblies. a. MainModule. and b.DataServerModule.

DataServerModule is referring to MainModule. And main module should not be
dependent on DataServerModule. Reason is, DataServerModule can be replaced
by another module in the future.
But the DataServerModule should be dynamically callable by MainModule.
The DataServerModule has classes implementing few Interfaces. On these
interfaces the MainModule will make method calls.

The DataServerModule is also implementing a Callback Interface Object which
will be used by remote clients to send data by calling methods on it.
For this I need to publish the Callback Object.

This is the Scenario.

First I was planning to Host both Modules in separate applications so that I
can achieve the MainModule's independency but the DataServerModule again had
to have an access to MainModule and its objects. So I could not move these
two assemblies to two different processes. If I do then it means, More
remoting objects on both the assemblies. More metadata dlls (like your
ShareDLL).

So, I was trying to use reflection to get the DataServerModule loaded.
I was assuming if the publishing is done by the Callback Object itself, the
MainModule is totally independent of handling DataServerModule.

Without using Reflection publishing from the object itself works fine. But
when I do the same looks like Publishing fails.

I think now you have a good idea of what I am trying to achieve.

Thanks,
Livingston.