Remoting Dilemma

[ckkwan]

I am kind of stucked.

App A -> Remoting DLL <- App B
(Server) (Client)


Application A will invoke the Remoting DLL and start it as a server.

There will have multiple Application B (clients) trying to connect.

Well, they all can connect without any problem, but!

The Remoting DLL cannot have access to Application A (which stores
some critical information).

I can¡¦t reference Application A into Remoting Dll, because App A is
not a DLL, and even if I am able to do so it will cause a circular
reference.

In C++ there is something like forward declaration and extern the
instance. So, what is the solution for C# here?

Thanks in advance ļ

 

[sloan]

Are you talking about keeping your secret code safe?

Or the cyclic reference issue?

Take a look here:
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!122.entry
and there is a URL at this blog pointing to another site (secretgeek)

...

However, I suggest WCF over .Net Remoting for any "new" code projects.

...




I am kind of stucked.

App A -> Remoting DLL <- App B
(Server) (Client)


Application A will invoke the Remoting DLL and start it as a server.

There will have multiple Application B (clients) trying to connect.

Well, they all can connect without any problem, but!

The Remoting DLL cannot have access to Application A (which stores
some critical information).

I can¡¦t reference Application A into Remoting Dll, because App A is
not a DLL, and even if I am able to do so it will cause a circular
reference.

In C++ there is something like forward declaration and extern the
instance. So, what is the solution for C# here?

Thanks in advance ļ