| Groups | Blog | Home |
dotnet clr : Help! I need to prevent .NET exception dialogs from displaying.
[quoted text, click to view] "Ken Varn" <varnk@diebold.com> wrote in message news:euxNpK1aDHA.3360@tk2msftngp13.phx.gbl... > I have an unattended 24/7 system that runs a few .NET applications. I > really need to prevent any unhandled exceptions from displaying the > exception dialog box. I want the application to just terminate. This was > available with Dr. Watson, but I can't figure out how to do it for .NET > apps. Can someone please tell me how to disable .NET exception dialogs? No > code changes please. I would prefer registry setting if possible. > You should prevent unattended applications from throwing unhandled exceptions. In your Main, and any ThreadProc, and any method which is the target of a callback, run all code inside a try/catch block, log the exception and/or write an event and let the method terminate. David
I have an unattended 24/7 system that runs a few .NET applications. I
really need to prevent any unhandled exceptions from displaying the exception dialog box. I want the application to just terminate. This was available with Dr. Watson, but I can't figure out how to do it for .NET apps. Can someone please tell me how to disable .NET exception dialogs? No code changes please. I would prefer registry setting if possible. -- ----------------------------------- Ken Varn Senior Software Engineer Diebold Inc. varnk@diebold.com -----------------------------------
I keep getting the same response for this question. Please read the
original question. Changing the source for some of the applications is not an option. I want what was available with Dr. Watson. I want to disable all .NET unhandled exception dialogs. Is there a way to do this? Developers at Microsoft need to realize that just because they do not think a feature is worth keeping around, doesn't mean that the rest of the programming world doesn't use it. Sorry for spouting off, but this is really getting aggravating. -- ----------------------------------- Ken Varn Senior Software Engineer Diebold Inc. varnk@diebold.com ----------------------------------- "David Browne" <davidbaxterbrowne no potted meat@hotmail.com> wrote in message news:%23Uvz5n1aDHA.2404@TK2MSFTNGP10.phx.gbl... [quoted text, click to view] > > "Ken Varn" <varnk@diebold.com> wrote in message > news:euxNpK1aDHA.3360@tk2msftngp13.phx.gbl... > > I have an unattended 24/7 system that runs a few .NET applications. I > > really need to prevent any unhandled exceptions from displaying the > > exception dialog box. I want the application to just terminate. This was > > available with Dr. Watson, but I can't figure out how to do it for .NET > > apps. Can someone please tell me how to disable .NET exception dialogs? > No > > code changes please. I would prefer registry setting if possible. > > > > You should prevent unattended applications from throwing unhandled > exceptions. > > In your Main, and any ThreadProc, and any method which is the target of a > callback, run all code inside a try/catch block, log the exception and/or > write an event and let the method terminate. > > David > >
[quoted text, click to view]
>I keep getting the same response for this question. Please read the >original question. Changing the source for some of the applications is not >an option. Well, maybe you keep getting the same answer because that's the only answer that works ! I don't see any way to simply suppress all exception dialogs - either *YOU* handle them in your code, or they'll pop up. Can't have the cake and eat it, too ! Marc ================================================================ Marc Scheuner May The Source Be With You!
can't you write a "loader" utility which uses Reflection.Assmbly to load
your app and run it (unchanged), enclosed in a try-catch? [quoted text, click to view] Ken Varn wrote:
> I keep getting the same response for this question. Please read the > original question. Changing the source for some of the applications is not > an option. I want what was available with Dr. Watson. I want to disable > all .NET unhandled exception dialogs. Is there a way to do this? > > Developers at Microsoft need to realize that just because they do not think > a feature is worth keeping around, doesn't mean that the rest of the > programming world doesn't use it. > > Sorry for spouting off, but this is really getting aggravating. >
[quoted text, click to view] "Ken Varn" <varnk@diebold.com> wrote in message news:eFea1T$cDHA.1540@tk2msftngp13.phx.gbl... > Well, put this in the suggestion box. It was available with regular C++ > programming through Dr. Watson. It would seem there is no equivalent > exception handling application. > > What would you propose that I do for .NET applications that are 3rd party? Don't use them for purposes for which they weren't designed. If they allow popups, then they weren't designed for unattended execution. [quoted text, click to view] > I can't guarantee that all applications handle all exceptions. >My system is > a critical 24/7 system that is unattended. When these pop-up dialogs > appear, it suspends operations until someone acknowledges the modal dialog > box. This is unacceptable for an unattended system. > It is simply unacceptable for an unattended application to generate a popup, and unacceptable to incorporate any application that does into an unattended system. Now that being said Dr.Watson wasn't made of magic. You can enumerate processes and windows and read window text and send window messages that correspond to button clicks. It's just not easy. David
Well, put this in the suggestion box. It was available with regular C++
programming through Dr. Watson. It would seem there is no equivalent exception handling application. What would you propose that I do for .NET applications that are 3rd party? I can't guarantee that all applications handle all exceptions. My system is a critical 24/7 system that is unattended. When these pop-up dialogs appear, it suspends operations until someone acknowledges the modal dialog box. This is unacceptable for an unattended system. -- ----------------------------------- Ken Varn Senior Software Engineer Diebold Inc. varnk@diebold.com ----------------------------------- [quoted text, click to view] "Marc Scheuner [MVP ADSI]" <m.scheuner@inova.SPAMBEGONE.ch> wrote in message news:80qokv8h6r3j83fdhbif5qlvibodaht2e5@4ax.com... > >I keep getting the same response for this question. Please read the > >original question. Changing the source for some of the applications is not > >an option. > > Well, maybe you keep getting the same answer because that's the only > answer that works ! I don't see any way to simply suppress all > exception dialogs - either *YOU* handle them in your code, or they'll > pop up. > > Can't have the cake and eat it, too ! > > Marc > ================================================================ > Marc Scheuner May The Source Be With You! > Bern, Switzerland m.scheuner(at)inova.ch
[quoted text, click to view]
>What would you propose that I do for .NET applications that are 3rd party? >I can't guarantee that all applications handle all exceptions. My system is >a critical 24/7 system that is unattended. When these pop-up dialogs >appear, it suspends operations until someone acknowledges the modal dialog >box. This is unacceptable for an unattended system. One way would be to write a small C# "loader" that would load / execute those third-party apps/components, and that would implement a "catch-all" exception handler that would catch, record, and "swallow" all exceptions that show up. However, if the third-party app *itself* catches an exception and displays an error message box, you're out of luck - you won't be able to change the behaviour of that app from the outside, I'd say. Not sure if maybe the MS Exception Handling Application Block could be of use to you, too - I've looked at it, but it looked rather complicated and convoluted, so I backed off - it should allow you to define certain ways of handling exceptions (e.g. by just recording them to a log file etc.). http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/emab-rm.asp Marc ================================================================ Marc Scheuner May The Source Be With You!
I am not talking about trapping all dialog boxes and error messages. I
merely want to stop the display of the unhandled exception dialog that the clr displays. That does not seem to be asking too much. If for some reason an application left out a catch for unhandled exceptions, there should be a way for the clr unhandled exception handler settings to be modified (outside of source code) to not display the dialog box and just log the error to the event viewer. -- ----------------------------------- Ken Varn Senior Software Engineer Diebold Inc. varnk@diebold.com ----------------------------------- "David Browne" <davidbaxterbrowne no potted meat@hotmail.com> wrote in message news:%23DOZNc$cDHA.3520@tk2msftngp13.phx.gbl... [quoted text, click to view] > > "Ken Varn" <varnk@diebold.com> wrote in message > news:eFea1T$cDHA.1540@tk2msftngp13.phx.gbl... > > Well, put this in the suggestion box. It was available with regular C++ > > programming through Dr. Watson. It would seem there is no equivalent > > exception handling application. > > > > What would you propose that I do for .NET applications that are 3rd party? > > Don't use them for purposes for which they weren't designed. > If they allow popups, then they weren't designed for unattended execution. > > > I can't guarantee that all applications handle all exceptions. > >My system is > > a critical 24/7 system that is unattended. When these pop-up dialogs > > appear, it suspends operations until someone acknowledges the modal dialog > > box. This is unacceptable for an unattended system. > > > > It is simply unacceptable for an unattended application to generate a popup, > and unacceptable to incorporate any application that does into an unattended > system. > > Now that being said Dr.Watson wasn't made of magic. You can enumerate > processes and windows and read window text and send window messages that > correspond to button clicks. It's just not easy. > > David > >
I'll look into these suggestions. Thanks.
I still think that Microsoft should have provided a registry setting or something to disable the clr unhandled exception dialog box. -- ----------------------------------- Ken Varn Senior Software Engineer Diebold Inc. varnk@diebold.com ----------------------------------- [quoted text, click to view] "Marc Scheuner [MVP ADSI]" <m.scheuner@inova.SPAMBEGONE.ch> wrote in message news:r37olvk5fj80ghsdjnbhd5r7khsr6gkbq9@4ax.com... > >What would you propose that I do for .NET applications that are 3rd party? > >I can't guarantee that all applications handle all exceptions. My system is > >a critical 24/7 system that is unattended. When these pop-up dialogs > >appear, it suspends operations until someone acknowledges the modal dialog > >box. This is unacceptable for an unattended system. > > One way would be to write a small C# "loader" that would load / > execute those third-party apps/components, and that would implement a > "catch-all" exception handler that would catch, record, and "swallow" > all exceptions that show up. > > However, if the third-party app *itself* catches an exception and > displays an error message box, you're out of luck - you won't be able > to change the behaviour of that app from the outside, I'd say. > > Not sure if maybe the MS Exception Handling Application Block could be > of use to you, too - I've looked at it, but it looked rather > complicated and convoluted, so I backed off - it should allow you to > define certain ways of handling exceptions (e.g. by just recording > them to a log file etc.). > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/emab-rm.asp > > Marc > ================================================================ > Marc Scheuner May The Source Be With You! > Bern, Switzerland m.scheuner(at)inova.ch
Ken,
Look under: HKLM\SOFTWARE\Microsoft\NETFramework The DbgManagedDebugger value determines which program runs when an unhandled exception is thrown. Also, look at the DbgJITDebugLaunchSetting value. Setting this value to 0 will bring up the default message box. 1 will prevent the JIT handler from running. 2 will cause the program to try to keep running. If the unhandled exception is a Win32 exception, look at HTML\Software\Microsoft\Windows NT\CurrentVersion\AeDebug key. See O'Reilly's excellent Mastering Visual Studio.NET (p86) for more details. Hope this helps. - Ben Blair - benblair@Association for Computing Machinery dot org [quoted text, click to view] >-----Original Message----- ===========================================================>I'll look into these suggestions. Thanks. > >I still think that Microsoft should have provided a registry setting or >something to disable the clr unhandled exception dialog box. > >-- >----------------------------------- >Ken Varn >Senior Software Engineer >Diebold Inc. >varnk@diebold.com >----------------------------------- >"Marc Scheuner [MVP ADSI]" <m.scheuner@inova.SPAMBEGONE.ch> wrote in message >news:r37olvk5fj80ghsdjnbhd5r7khsr6gkbq9@4ax.com... >> >What would you propose that I do for .NET applications that are 3rd >party? >> >I can't guarantee that all applications handle all exceptions. My system >is >> >a critical 24/7 system that is unattended. When these pop-up dialogs >> >appear, it suspends operations until someone acknowledges the modal >dialog >> >box. This is unacceptable for an unattended system. >> >> One way would be to write a small C# "loader" that would load / >> execute those third-party apps/components, and that would implement a >> "catch-all" exception handler that would catch, record, and "swallow" >> all exceptions that show up. >> >> However, if the third-party app *itself* catches an exception and >> displays an error message box, you're out of luck - you won't be able >> to change the behaviour of that app from the outside, I'd say. >> >> Not sure if maybe the MS Exception Handling Application Block could be >> of use to you, too - I've looked at it, but it looked rather >> complicated and convoluted, so I backed off - it should allow you to >> define certain ways of handling exceptions (e.g. by just recording >> them to a log file etc.). >> >> >http://msdn.microsoft.com/library/default.asp? url=/library/en-us/dnbda/html/emab-rm.asp >> >> Marc >> ===== [quoted text, click to view] >> Marc Scheuner May The Source Be
With You! >> Bern, Switzerland m.scheuner(at) inova.ch > > >.
Finally my question is answered! Thank you! Thank you!
This is exactly what I was looking for. -- ----------------------------------- Ken Varn Senior Software Engineer Diebold Inc. varnk@diebold.com ----------------------------------- "Ben Blair" <benblair@Association_for_Computing_Machinery.org> wrote in message news:39ae01c37bd9$c9121130$a501280a@phx.gbl... [quoted text, click to view] > Ken, > Look under: > HKLM\SOFTWARE\Microsoft\NETFramework > The DbgManagedDebugger value determines which program runs > when an unhandled exception is thrown. Also, look at the > DbgJITDebugLaunchSetting value. Setting this value to 0 > will bring up the default message box. 1 will prevent the > JIT handler from running. 2 will cause the program to try > to keep running. > > If the unhandled exception is a Win32 exception, look at > HTML\Software\Microsoft\Windows NT\CurrentVersion\AeDebug > key. > > See O'Reilly's excellent Mastering Visual Studio.NET (p86) > for more details. > > Hope this helps. > > - Ben Blair > - benblair@Association for Computing Machinery dot org > > >-----Original Message----- > >I'll look into these suggestions. Thanks. > > > >I still think that Microsoft should have provided a > registry setting or > >something to disable the clr unhandled exception dialog > box. > > > >-- > >----------------------------------- > >Ken Varn > >Senior Software Engineer > >Diebold Inc. > >varnk@diebold.com > >----------------------------------- > >"Marc Scheuner [MVP ADSI]" > <m.scheuner@inova.SPAMBEGONE.ch> wrote in message > >news:r37olvk5fj80ghsdjnbhd5r7khsr6gkbq9@4ax.com... > >> >What would you propose that I do for .NET applications > that are 3rd > >party? > >> >I can't guarantee that all applications handle all > exceptions. My system > >is > >> >a critical 24/7 system that is unattended. When these > pop-up dialogs > >> >appear, it suspends operations until someone > acknowledges the modal > >dialog > >> >box. This is unacceptable for an unattended system. > >> > >> One way would be to write a small C# "loader" that > would load / > >> execute those third-party apps/components, and that > would implement a > >> "catch-all" exception handler that would catch, record, > and "swallow" > >> all exceptions that show up. > >> > >> However, if the third-party app *itself* catches an > exception and > >> displays an error message box, you're out of luck - you > won't be able > >> to change the behaviour of that app from the outside, > I'd say. > >> > >> Not sure if maybe the MS Exception Handling Application > Block could be > >> of use to you, too - I've looked at it, but it looked > rather > >> complicated and convoluted, so I backed off - it should > allow you to > >> define certain ways of handling exceptions (e.g. by > just recording > >> them to a log file etc.). > >> > >> > >http://msdn.microsoft.com/library/default.asp? > url=/library/en-us/dnbda/html/emab-rm.asp > >> > >> Marc > >> > =========================================================== > ===== > >> Marc Scheuner May The Source Be > With You! > >> Bern, Switzerland m.scheuner(at) > inova.ch > > > > > >. > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |