Vista - Unhandled Exception in Console Application

Can anyone point me to an example or info on handling unhandled exceptions
in a console application?
Preferrably VB.

Thanks,

--

AG
Email: discussATadhdataDOTcom

On Tue, 08 Apr 2008 13:34:30 -0700, AG <NOSPAMagiamb@xxxxxx>
wrote:
The MSDN documentation for the AppDomain.UnhandledException event has lots
of information and a code sample:
http://msdn2.microsoft.com/en-us/lib...exception.aspx

Thanks for the quick reply.
That looks good. I will try it.

--

AG
Email: discussATadhdataDOTcom
"Peter Duniho" <NpOeStPeAdM@xxxxxx> wrote in message
newsp.t9banlie8jd0ej@xxxxxx-computer.local...

That enables me to log the exception, but how can I prevent the Windows
'Myapp has encountered a problem and needs to close...' dialog from popping
up?

--

AG
Email: discussATadhdataDOTcom
"Peter Duniho" <NpOeStPeAdM@xxxxxx> wrote in message
newsp.t9banlie8jd0ej@xxxxxx-computer.local...

you can try
if (Args.IsTerminating) Environment.Exit (0) ;

where Args is your UnhandledExceptionEventArgs

/LM

"AG" <NOSPAMagiamb@xxxxxx> wrote in message
news:%23GQmlQkmIHA.5268@xxxxxx

On Wed, 09 Apr 2008 06:18:04 -0700, AG <NOSPAMagiamb@xxxxxx>
wrote:
You can try the solution Luc suggested. I'd say there's at least a 50/50
chance it'll work (I'd test it myself, but I figure you can do that just
as easily, and at the moment I am doing other things ).

If it doesn't, then you may not be able to prevent the dialog from
appearing.

Of course, this assumes the exception is happening somewhere that you are
unable to provide your own try/catch block in order to handle the
exception. Your original question implies this, but if it's not really
true, then obviously the best solution is to actually handle the
exception.

Pete

Thanks both.
That works.
I haven't done a console app before and It is a very small one. I could
easily have wrapped that whole thing in a try/catch, but this way I learned
much more .

--

AG
Email: discussATadhdataDOTcom
"Luc E. Mistiaen" <luc.mistiaen@xxxxxx> wrote in message
news:e6$YxLlmIHA.5260@xxxxxx

Luc E. Mistiaen wrote:Be aware that this technique does not scale to services or multiple
appdomains, and it will also prevent you from diagnosing the unhandled
exception under a debugger (you can set a breakpoint on the event callback,
but that isn't convenient at all). Finally, the usual step of writing an
error to the event log will be skipped.

I also suggest passing a non-zero value to Environment.Exit(), since
processes that check the exit status (if any) will usually interpret a zero
exit status as success, which is a tad misleading.

In short, I'm not at all happy that this actually works. :-)

--
J.

Thanks for the info.
In this case it will be fine as the app is just for my own use.
However, I am interested in how you think it should be handled.

--

AG
Email: discussATadhdataDOTcom
"Jeroen Mostert" <jmostert@xxxxxx> wrote in message
news:47fd20a7$0$14342$e4fe514c@xxxxxx

> Finally, the usual step of writing an error to the event log will beI suppose it was precisely waht the OP intended to do: his own logging. You
just do it before exiting.
Of course, it was just an example.
Neither me, but its the only way I found to suppress the unwanted pop-up. I
would have much preferred some boolean to be set in the argument object to
tell the run-time I handled to event to my taste (knowing that the program
would terminate anyway).

/LM