Report a Silverlight Bug

Re: ApplicationUnhandledException not called.

jjy2 — Wed, 26 Sep 2007 17:50:40 GMT

I think I need to clarify this as I saw similar issues in the other posts

It seems we have 3 different but related issues

Debugger does not break non-user code -- which is normal behaviour as VladF pointed out
When there are uncaughted exceptions, sometimes framework emits the error message with messagebox sometimes it doesn't.
WebApplication.Current.ApplicationUnhandledException event suggested by its name that we can handle unhandled exception using this event but this event is sometimes called and sometimes not.

Re: ApplicationUnhandledException not thrown

jjy2 — Tue, 25 Sep 2007 09:37:10 GMT

Hi VladF

Thanks for that. I now enabled just about every type of break in debugger.

But I still need ApplicationUnhandledException to be called at runtime so that my application can take appropriate action.
Hope this will be fixed in the release

Re: ApplicationUnhandledException not thrown

VladF — Mon, 24 Sep 2007 20:41:40 GMT

Menu Debug | Exceptions -> check all the checks you need. For some reason they are unchecked by default.

ApplicationUnhandledException not thrown

jjy2 — Thu, 20 Sep 2007 08:01:10 GMT

ApplicationUnhandledException is not called if user codes throw exception during particular event handling
(such as Loaded, MouseLeftButtonDown etc..)

It seems it's caught inside framework and codes executes continusly as if nothing happened.

I got it working only if javascript calls C# class object's method and if I throw an exception in that method.

I realized that I have to put try--cath in almost every event handling routines.

Is this by design?