Why no error pop-ups in my multi-threaded application?

[eBob.com]

I get no error pop-ups from my multi-threaded application. This makes it
difficult to find errors. Fortunately I can step statement by statement
though code running under any thread - but that's a lot slower than a pop-up
allowing you to "break" and go directly to the offending statement. I've
done searches but I have not been able to find any discussion of this
problem. Is this a common problem or unique to my system/application?

Thanks, Bob

 

[Guest]

Bob,

What IDE are you running? For example, I don't believe you have full
debugging capabilities for multi-threaded apps in the Express Editions.

Kerry Moorman

 

[eBob.com]

Thanks Kerry, I meant to add that info but then forgot to.

I am running Microsoft Development Environment 2003 V 7.1.3088,
Microsoft .NET Framework 1.1 V 1.1.4322, and Microsoft Visual Basic .NET
69462-335-0000007-18875.

Thanks, Bob

 

[rowe_newsgroups]

I get no error pop-ups from my multi-threaded application. This makes it
difficult to find errors. Fortunately I can step statement by statement
though code running under any thread - but that's a lot slower than a pop-up
allowing you to "break" and go directly to the offending statement. I've
done searches but I have not been able to find any discussion of this
problem. Is this a common problem or unique to my system/application?

Thanks, Bob

Watch your output window, it's possible you are actually catching an
exception in a try...catch block which will prevent the error pop-up.
If so, the output window usually writes a "First chance exception of
type XXX was thrown" or something similar. Then you just have to find
where it occurred. I try to use Debug.Assert(...) to test critical
parts of my application, especially in multithreaded solutions. Also,
using Debug.Write(...) can be nice for writing out status messages and
to track where things went sour.

Thanks,

Seth Rowe