 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / CLR / October 2005using AppDomain.DoCallBack() asynchronously?
if i want to call into another AppDomain with messing with Remoting, i can use the AppDomain.DoCallBack() passing in a CrossAppDomainDelegate. But this executes synchronously. Is there a way i can call into another AppDomain asynchronously, but without having mess with Remoting? > if i want to call into another AppDomain with messing with Remoting, i can > use the AppDomain.DoCallBack() passing in a CrossAppDomainDelegate. But this > executes synchronously. Is there a way i can call into another AppDomain > asynchronously, but without having mess with Remoting? The only thing you need is a MarshalByRefObject from the another domain. Then you can simply "callback" using a method of that MBR. Rob > if i want to call into another AppDomain with messing with Remoting, i can > use the AppDomain.DoCallBack() passing in a CrossAppDomainDelegate. But this > executes synchronously. Is there a way i can call into another AppDomain > asynchronously, but without having mess with Remoting? create a delegate to the method that calls DoCallBack, and execute it asynchronously. or use ThreadPool.QueueUserWorkItem.  Signaturei'm midnightbeach.com and a mtn bike accident means i'm left handed until mid october, so please pardon lower case and terseness. Right, but then that delegate will execute in the main appdomain, not the newly created appdomain. Or do you mean call DoCallBack to get into the new appdomain, and then once in the new appdomain, make an async delegate call to kick off the new thread. that would do what i want. Then the main thread would return back to the main appdomain and there would be a new thread running in the new appdomain. well, either way you meant you got me in the right direction :-) thanks, John > > if i want to call into another AppDomain with messing with Remoting, i can > > use the AppDomain.DoCallBack() passing in a CrossAppDomainDelegate. But this [quoted text clipped - 3 lines] > create a delegate to the method that calls DoCallBack, and execute it > asynchronously. or use ThreadPool.QueueUserWorkItem. Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.