Reason for Application.ThreadExit

Hi,

We have the strange problem that sometime in our application
Application.ThreadExit is raised and out application shutting down.

We do not see any previous exceptions before this event fires.

Moreover the Application.ThreadException event is not fired at all, so
we have not unhandled exceptions that occurs.

We are working with SQL-2005 and with some unmanaged code too.

What can be the reason for such behaviour ? And how can we catch such
error ?

Thanks,
Pavel

Richard
Mon Jan 15 18:40:17 CST 2007

Hi,

How do you know the exception is occuring if you cannot catch it? Are you
receiving a dialog? What version of the framework are you using? Are you
aware that unhandled exceptions wont be caught in debug mode? Why do you
include sql 2005 plus unmanaged in your problem? Does the problem occur when
accessing code paths involving these services or is it just totally random?

Richard

<pavel.orehov@gmail.com> wrote in message
news:1168867909.217511.100110@m58g2000cwm.googlegroups.com...
> Hi,
>
> We have the strange problem that sometime in our application
> Application.ThreadExit is raised and out application shutting down.
>
> We do not see any previous exceptions before this event fires.
>
> Moreover the Application.ThreadException event is not fired at all, so
> we have not unhandled exceptions that occurs.
>
> We are working with SQL-2005 and with some unmanaged code too.
>
> What can be the reason for such behaviour ? And how can we catch suchR
> error ?
>
> Thanks,
> Pavel
>

pavel
Sun Jan 21 12:57:46 CST 2007

> How do you know the exception is occuring if you cannot catch it?

I am registering to Application.ThreadExit &
Application.ThreadException. The ThreadExit fires without
ThreadException. I am not sure this was exception, but why ThreadExit
fires ?

> Are you receiving a dialog?

No

> What version of the framework are you using?

3.0

> Are you aware that unhandled exceptions wont be caught in debug mode?

I know, but the problem that there are no exceptions, just thread exit.

> Why do you include sql 2005 plus unmanaged in your problem? Does the problem occur when
accessing code paths involving these services or is it just totally
random?

Random.

My main question is what can cause to main thread of Windows Forms
raise ThreadExit without rasing ThreadException before ?

Andy
Mon Jan 22 15:10:25 CST 2007

ThreadExit just means the thread is shutting down, usually due to the
application ending. The ExitThread method would cause this to be
raised, as well as the last form closing.

pavel.orehov@gmail.com wrote:
> My main question is what can cause to main thread of Windows Forms
> raise ThreadExit without rasing ThreadException before ?