Thanks for your reply Phillip,

For the two questions you mentioned:

** The error in first message seems related to a VS managed debug
assistant. I've searched some former issue and found an existing record,
you can have a look at the following description and test it to see whether
if fits your case:

*** Problem Description ***
The CLR has been unable to transition from COM context 0x1a3608 to COM
context
0x1a3778 for 60 seconds. The thread that owns the destination
context/apartment is
most likely either doing a non pumping wait or processing a very long
running
operation without pumping Windows messages. This situation generally has a
negative
performance impact and may even lead to the application becoming non
responsive or
memory usage accumulating continually over time. To avoid this problem, all
single
threaded apartment (STA) threads should use pumping wait primitives (such
as
CoWaitForMultipleHandles) and routinely pump messages during long running
operations.

*** Resolution *** 08/28/2006 tqchen

This sounds like the ContextSwitchDeadlock Managed Debugging Assistant
(MDA). It can be deactivated by going into Debug | Exceptions and then
uncheck ContextSwitchDeadlock underneath Managed Debugging Assistants.
It can also be deactivated via the app.config. But, I wouldn't just
blindly deactivate this MDA without at least knowing why it's
occurring.
<<<<<<<<<<<<<<<<<<<<<<<<<<

For your second question, if you want to get return value, here is one
means I usually use:

Declare a wrapper class (maybe named ThreadWorker), it has some member
variables that will be used or share data during a thread's execution and
end. And it also contains the member function which is the thread proc.  
e.g.

public class ThreadWorker
{
public string Data;
//... other data

public void DoWork()
{
you can update any of the class members here.
.........
}
}

And whenever you want to start a new thread and do some work. YOu can first
create an instance of "ThreadWorker" and use its member function as
threadProc function. Then, after thread finished execution, you can get any
updated data from the class's member variable.  How do you think?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

within

problem

after

debugger