Why is the exception in my delegate ignored?

[james]

When I compile and run this code outside of Visual Studio no exception
is reported to the console and the program continues to run.

class Program
{

static void Main(string[] args)
{
System.Timers.Timer t = new System.Timers.Timer(10);
t.Elapsed += delegate { throw new Exception("Kaboom"); };
t.Start();

Console.ReadLine();
}
}

Any ideas?

Thanks,
James

[Peter Duniho]

On Mon, 02 Apr 2007 09:47:59 -0700, james <ja********@gmail.comwrote:

When I compile and run this code outside of Visual Studio no exception
is reported to the console and the program continues to run.

As far as I know, that's "by design". That is, since you have no
exception handler in the new thread, there's no code to detect the
exception and so the thread just exits (abnormally) without notice.

Pete

[james]

Thanks Pete. Along with that would anyone mind telling me the best
way to have that exception blow up my application? Is there a way
that would work with AppDomain.CurrDomain.UnhandledException?

Thanks,
James

[Jon Skeet [C# MVP]]

Peter Duniho <Np*********@nnowslpianmk.comwrote:

On Mon, 02 Apr 2007 09:47:59 -0700, james <ja********@gmail.comwrote:

When I compile and run this code outside of Visual Studio no exception
is reported to the console and the program continues to run.

As far as I know, that's "by design". That is, since you have no
exception handler in the new thread, there's no code to detect the
exception and so the thread just exits (abnormally) without notice.

The fact that it's running from a timer is significant though. In .NET
2.0, if a new "plain" thread throws an exception, it will abort the
program. Try this:

using System;

class Program
{
static void Main(string[] args)
{

new System.Threading.Thread(Foo).Start();

Console.ReadLine();
}

static void Foo()
{
throw new Exception();
}
}

In .NET 1.1 (IIRC) this wouldn't stop the program, but in .NET 2.0 it
does. From a *very* quick bit of experimentation, it looks like
threadpool threads throwing exceptions doesn't cause the program to
terminate, and System.Timers.Timer runs on thread pool threads. That
could be an over-simplification though...

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Michael Nemtsev]

Hello James,

Yep, you can use this (or Application.ThreadException for winforms)
Take into account that not all unhandled exceptions in threads terminate
thread and shutdown hosting process - ThreadAbortException is out of this
fule, afaik

---
WBR, Michael Nemtsev [C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

JThanks Pete. Along with that would anyone mind telling me the best
Jway to have that exception blow up my application? Is there a way
Jthat would work with AppDomain.CurrDomain.UnhandledException?
J>
JThanks,
JJames