I'm actually using HTTP, because this application needs to work from all over the world, and http traffic is very rarely blocked. I figured my chances of sending out an HTTP request from a hotels broadband system was higher than trying to connect to a different port using TCP.
Dino -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Mark Hurd Sent: Saturday, 14 October 2006 12:50 To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Get an AppDomain you didn't create On 10/14/06, Dean Cleaver <[EMAIL PROTECTED]> wrote: > Mike, > > What I was trying to achieve in this post was to call from the second > AppDomain to the first AppDomain, and get it to create the remote > instances for me - to see if that would get around the remoting issue > - but it seems it won't because of pathing issues - but I'm not sure > if it was going to help anyway. Have you tried using the new IPC remoting classes in 2.0 instead of TCP? Regards, Mark Hurd, B.Sc.(Ma.)(Hons.) =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
