Hi All,
I have seen a few good behaviours for what to do in the case of those pesky
uncaught exceptions. and I want to build some of these mechanisms into my
Application that is currently out on the factory floor [enhancing peoples
lives - said almost hysterically].
What I'd like to do is catch that uncaught exception .. log the exception
info and then pop up a window that is counting down to an application re-start
that has a space for the operator to enter some info explaning just what
the crikeyJingo he did to my application... (grrrr users really delight in
blowing up apps .. and no amount of easter eggs placate them *sigh*) This
way I can
Problem / Opportunity 1:
What I dont know how to do is catch that uncaught exception. more specifically
'where' to add the handler. I use VS2005 and create my projects just using
the defaults. I'm assuming it probably needs to go in that poor forgotten
Program.cs file that I never look at ... or maybe not.
Can any-one please enlighten me on exactly what handler to create and more
impotantly WHERE do I put it (given a VS2005 default solution).
Problem / Opportunity 2:
The second problem is finding a neat way to restart the application. I have
a number of service apps that support the main app so I am expecting that
I shall get one of these to run a new instance of the app After its been
notified (as part of the above 'closing down' behaviour ) that I would like
a restart-thank-you-very-much ...
Is there as better way ? is there a .net pattern ? is there a "1-click create
application" with property "non-trivial" set ..
---------------------------------------------
[Sam Samson] - There is no greater folly than fixed price quoting.