HELP: Debugging ApplicationEvents.UnhandledException???

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Spam Catcher
    #1

    HELP: Debugging ApplicationEvents.UnhandledException???

    Hi all,

    When I'm debugging my application in VS.NET 2005, the debugger intercepts
    all unhandled exceptions and does not break into
    ApplicationEven ts.UnhandledExc eption.

    How do I debug ApplicationEven ts.UnhandledExc eption? I have some elaborate
    code in there which I would like to test.

    ApplicationEven ts.UnhandledExc eption only seems to be executed if I do not
    have a debugger attached.

    Thanks!
    Tags: None
    • Spam Catcher
      #2
      Re: HELP: Debugging ApplicationEven ts.UnhandledExc eption???

      Spam Catcher <spamhoneypot@r ogers.comwrote in
      news:Xns98DD7EC 354ADusenethone ypotrogers@127. 0.0.1:
      Hi all,
      >
      When I'm debugging my application in VS.NET 2005, the debugger
      intercepts all unhandled exceptions and does not break into
      ApplicationEven ts.UnhandledExc eption.
      >
      How do I debug ApplicationEven ts.UnhandledExc eption? I have some
      elaborate code in there which I would like to test.
      >
      ApplicationEven ts.UnhandledExc eption only seems to be executed if I do
      not have a debugger attached.
      >
      Thanks!
      >

      Just bumping up the post ... anyone know how?

      Thanks!

        Comment

        • RobinS
          #3
          Re: HELP: Debugging ApplicationEven ts.UnhandledExc eption???

          You could run it w/o debugging. (Debug/Start without debugging).

          Robin S.
          ---------------------------------
          "Spam Catcher" <spamhoneypot@r ogers.comwrote in message
          news:Xns98DEA79 B7211Fusenethon eypotrogers@127 .0.0.1...
          Spam Catcher <spamhoneypot@r ogers.comwrote in
          news:Xns98DD7EC 354ADusenethone ypotrogers@127. 0.0.1:
          >
          >Hi all,
          >>
          >When I'm debugging my application in VS.NET 2005, the debugger
          >intercepts all unhandled exceptions and does not break into
          >ApplicationEve nts.UnhandledEx ception.
          >>
          >How do I debug ApplicationEven ts.UnhandledExc eption? I have some
          >elaborate code in there which I would like to test.
          >>
          >ApplicationEve nts.UnhandledEx ception only seems to be executed if I do
          >not have a debugger attached.
          >>
          >Thanks!
          >>
          >
          >
          Just bumping up the post ... anyone know how?
          >
          Thanks!


            Comment

            • Spam Catcher
              #4
              Re: HELP: Debugging ApplicationEven ts.UnhandledExc eption???

              "RobinS" <RobinS@NoSpam. yah.nonewrote in
              news:IvadnS2NJP L3fUHYnZ2dnUVZ_ uSgnZ2d@comcast .com:
              You could run it w/o debugging. (Debug/Start without debugging).
              Yes I know that - But I want to debug :-)

                Comment

                • RobinS
                  #5
                  Re: HELP: Debugging ApplicationEven ts.UnhandledExc eption???


                  "Spam Catcher" <spamhoneypot@r ogers.comwrote in message
                  news:Xns98DECF6 F5BCEusenethone ypotrogers@127. 0.0.1...
                  "RobinS" <RobinS@NoSpam. yah.nonewrote in
                  news:IvadnS2NJP L3fUHYnZ2dnUVZ_ uSgnZ2d@comcast .com:
                  >
                  >You could run it w/o debugging. (Debug/Start without debugging).
                  >
                  Yes I know that - But I want to debug :-)
                  Maybe you could muck with the settings in Debug/Exceptions. I don't know
                  how to get it to bubble all the way up to the application and not just stop
                  where it has the exception. Too bad you can't turn debug mode on and off.

                  Robin S.


                    Comment

                    • Spam Catcher
                      #6
                      Re: HELP: Debugging ApplicationEven ts.UnhandledExc eption???

                      "RobinS" <RobinS@NoSpam. yah.nonewrote in
                      news:Npudnc3qX5 BkskDYnZ2dnUVZ_ umlnZ2d@comcast .com:
                      "Spam Catcher" <spamhoneypot@r ogers.comwrote in message
                      news:Xns98DECF6 F5BCEusenethone ypotrogers@127. 0.0.1...
                      >"RobinS" <RobinS@NoSpam. yah.nonewrote in
                      >news:IvadnS2NJ PL3fUHYnZ2dnUVZ _uSgnZ2d@comcas t.com:
                      >>
                      >>You could run it w/o debugging. (Debug/Start without debugging).
                      >>
                      >Yes I know that - But I want to debug :-)
                      >
                      Maybe you could muck with the settings in Debug/Exceptions. I don't
                      know how to get it to bubble all the way up to the application and not
                      just stop where it has the exception. Too bad you can't turn debug
                      mode on and off.
                      Already tried ... Someone in here must know? :-)

                        Comment

                        • Randy
                          #7
                          Re: HELP: Debugging ApplicationEven ts.UnhandledExc eption???

                          I'm just a beginner so take this with a grain of salt:
                          I think you want to test your exception handlers? What about using Err.Raise
                          Example:
                          Try
                          Err.Raise(61) 'raise disk full error
                          Catch when Err.Number = 61
                          MsgBox("Error: Disk is full")
                          End Try

                          Randy

                          "Spam Catcher" <spamhoneypot@r ogers.comwrote in message
                          news:Xns98DEA79 B7211Fusenethon eypotrogers@127 .0.0.1...
                          Spam Catcher <spamhoneypot@r ogers.comwrote in
                          news:Xns98DD7EC 354ADusenethone ypotrogers@127. 0.0.1:
                          >
                          >Hi all,
                          >>
                          >When I'm debugging my application in VS.NET 2005, the debugger
                          >intercepts all unhandled exceptions and does not break into
                          >ApplicationEve nts.UnhandledEx ception.
                          >>
                          >How do I debug ApplicationEven ts.UnhandledExc eption? I have some
                          >elaborate code in there which I would like to test.
                          >>
                          >ApplicationEve nts.UnhandledEx ception only seems to be executed if I do
                          >not have a debugger attached.
                          >>
                          >Thanks!
                          >>
                          >
                          >
                          Just bumping up the post ... anyone know how?
                          >
                          Thanks!

                            Comment

                            • Spam Catcher
                              #8
                              Re: HELP: Debugging ApplicationEven ts.UnhandledExc eption???

                              "Randy" <ac7nj@comcast. netwrote in
                              news:D5OdnUqpfp RR9ELYnZ2dnUVZ_ qWvnZ2d@comcast .com:
                              I'm just a beginner so take this with a grain of salt:
                              I think you want to test your exception handlers? What about using
                              Err.Raise Example:
                              Try
                              Err.Raise(61) 'raise disk full error
                              Catch when Err.Number = 61
                              MsgBox("Error: Disk is full")
                              End Try
                              Hi Randy, I'm already testing my exceptions through out my application.

                              I would like to debug my global exception handler (for cases where my error
                              handling falls through).

                              Unfortunately it seems while in debug mode, VS.NET takes over the global
                              handler... and doesn't allow me to debug my custom code :-(

                                Comment

                                Previous template Next
                                Working...