You've tried setting up the method in a separate AppDomain and aborting the domain? Why doesn't it work? Do you mean you can't set up the domain or that not all the threads get terminated? (The latter problem could only happen if the method you are calling spawns its own AppDomains, or spawns unmanaged threads).
There is one other possibility you could try, but I warn you it is _very_ dangerous: Use the ProcessThread class to enumerate over the physical threads in the process immediately before calling the method and again after calling it. Then assume all the new threads that appear have been created by the method - and do an unmanaged TerminateThread on them. You risk losing information because of threads not cleaning up properly. And you risk killing some other thread that has nothing to do with this method you are calling (eg. if the CLR happened to internally creat a thread at about the same time). But as a last resort you might be able to do something with that idea. Simon ----------------------------------------------------------- Simon Robinson http://www.SimonRobinson.com ----------------------------------------------------------- ----- Original Message ----- From: "pralay" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 19, 2002 7:13 AM Subject: Re: [ADVANCED-DOTNET] Accessing child thread from parent thread > Hi Gert, > I've tried that also. But it doesn't work. > Pralay > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
