I have an app that uses a thirdpart library, this thirdparty library
creates an appdomain (totally out of my control), this new appdomain
loads some assemblies I created and this code I created needs to talk
back to the first app that started it all.
All the examples of cross appdomain communications I see assume that my
code is creating the new appdomain but thats not the case for me. Is
there a way for my two pieces of code to talk to each other? I know I
can do tcp remoting to 127.0.0.1 but I was hoping there would be
something much simpler!

To make things clearer. Application X on appdomain J loads assembly Y
which creates its own appdomain K, K loads assembly Z which needs to
talk to back to X but X is on appdomain J while Z is on appdomain K. I
have no control over the code on Y.

Thanks for any info!

Hi cs,

Regardless of the configuration they easiest way to communicate between
AppDomains is to use a CrossAppDomainDelegate.

If you have no control over one piece os code and it doesn't define a
way of communicating with it then your pretty much stuffed. But that
obviouse really.

Hope that helps,
Jan