Unhandled Exception Handler in.NET 1.1

I'm keeping a.NET 1.1 application and also among things I've been entrusted with is seeing to it the customer does not see any kind of hostile mistake alerts.

I've included trainers to Application.ThreadException and also AppDomain.CurrentDomain.UnhandledException, which do get called. My trouble is that the typical CLR mistake dialog is still presented (prior to the exception trainer is called).

Jeff speaks about this trouble on his blog site here and also here. Yet there's no remedy. So what is the typical means in.NET 1.1 to take care of uncaught exemptions and also display a pleasant dialog box?

Jeff's feedback was noted as the proper solution due to the fact that the link he gave has one of the most full details on just how to do what's called for.

0
2019-05-03 18:01:41
Source Share
Answers: 4

Oh, in Windows Forms you most definitely need to have the ability to get it to function. The only point you need to look out for is points taking place on various strings.

I have an old Code Project write-up below which need to aid :

User Friendly Exception Handling

0
2019-05-08 20:44:52
Source

AppDomain.UnhandledException is an occasion , not an international exception trainer. This suggests, by the time it is elevated, your application is currently on its means away, and also there is absolutely nothing you can do concerning it, with the exception of doing cleaning and also mistake logging.

What took place behind the scenes is this : The structure identified the exception, strolled up the call pile to the really leading, located no trainers that would certainly recoup from the mistake, so was incapable to establish if it was secure to proceed implementation. So, it began the closure series, and also discharged up this occasion as a politeness to you so you can pay your areas to your currently - doomed procedure. This takes place when an exception is left unhandled generally string.

There is no solitary - factor remedy to this sort of mistake. You require to place an actual exception trainer (a catch block) upstream of all areas where this mistake takes place and also onward it to (as an example) an international trainer method/class that will certainly establish if it is secure to merely report and also proceed, based upon exception type and/or web content.

Modify : It is feasible to disable (= hack) the mistake - coverage device constructed right into Windows so the required "crash and also melt" dialog does not get presented when your application drops. Nonetheless, this comes to be reliable for all the applications in the system, not simply your very own.

0
2019-05-08 17:38:34
Source

It's a Windows Forms application. The exemptions that are captured by Application.ThreadException job penalty, and also I do not get the ugly.NET exception box (OK to end, Cancel to debug? that thought of that?? ).

I was obtaining some exemptions that weren't being captured by that and also wound up mosting likely to the AppDomain.UnhandledException occasion that were creating troubles. I assume I've captured a lot of those exemptions, and also I am presenting them in our wonderful mistake box currently.

So I'll simply need to wish there are not a few other conditions that would certainly create exemptions to not be captured by the Application.ThreadException trainer.

0
2019-05-07 16:40:11
Source

Is this a console application or a Windows Forms application? If it's a.NET 1.1 console application this is, regretfully, deliberately-- it's validated by an MSFT dev in the second blog post you referenced :

BTW, on my 1.1 equipment the instance from MSDN does have the predicted result; it's simply that the 2nd line does not turn up till after you've affixed a debugger (or otherwise ). In v2 we've turned points around to make sure that the UnhandledException occasion fires prior to the debugger affixes, which appears to be what most individuals anticipate.

It appears like.NET 2.0 does this far better (give thanks to benefits ), yet truthfully, I never ever had time to return and also examine.

0
2019-05-07 16:33:40
Source