Code failing silently

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

    Code failing silently

    I seem to have acquired a strange issue here, some of my programs are
    now failing silently, resuming without notification that anything went
    wrong, both on my development machine and (I think) on the users
    machines. For instance, I was just noticing a spot where a table
    adapter's fill method fails, and the new form just opens up anyway
    after skipping the rest of the form's Load procedure without any
    indication anything went wrong. I haven't fiddled with any of the
    debug settings, and I don't remember if this started when I upgraded
    to VS 2008 or a while later. I am pretty sure it never happened in
    2005 though.

    What settings should I check or change to *make* it tell me something
    went wrong? Sorry, I know this makes me seem like a lame developer,
    it's just that the default debug settings have always worked fine for
    me so I don't know much about altering them.

    Bob Graham
    Tags: None
    • gerry
      #2
      Re: Code failing silently

      sounds like you have a try/catch somewhere that is throwing the exception
      away


      "RvGrah" <rvgrahamsevate nein@sbcglobal. netwrote in message
      news:c4853183-9c6e-4954-92c1-92b8370c9858@u6 g2000prc.google groups.com...
      >I seem to have acquired a strange issue here, some of my programs are
      now failing silently, resuming without notification that anything went
      wrong, both on my development machine and (I think) on the users
      machines. For instance, I was just noticing a spot where a table
      adapter's fill method fails, and the new form just opens up anyway
      after skipping the rest of the form's Load procedure without any
      indication anything went wrong. I haven't fiddled with any of the
      debug settings, and I don't remember if this started when I upgraded
      to VS 2008 or a while later. I am pretty sure it never happened in
      2005 though.
      >
      What settings should I check or change to *make* it tell me something
      went wrong? Sorry, I know this makes me seem like a lame developer,
      it's just that the default debug settings have always worked fine for
      me so I don't know much about altering them.
      >
      Bob Graham

        Comment

        • Michael Justin
          #3
          Re: Code failing silently

          gerry wrote:
          sounds like you have a try/catch somewhere that is throwing the exception
          away
          - or a BackgroundWorke r who silently "eats" the exception.

          --
          Michael Justin
          SCJP, SCJA
          betasoft - Software for Delphiâ„¢ and for the Javaâ„¢ platform
          http://www.mikejustin.com - http://www.betabeans.de

            Comment

            • RvGrah
              #4
              Re: Code failing silently

              Thx for the input, but these ideas I've already looked at..

              For instance, I'm getting this error:

              A first chance exception of type 'System.NullRef erenceException '
              occurred in GranPoSys.exe

              From this code line:

              ultraGridPrintD ocument1.Grid.D isplayLayout.Ap pearance.Border Color =
              Color.White;

              because the "grid" property of the ultraGridPrintD ocument had not been
              set. But, instead of breaking into the running code, the user
              interface just pops back up ready to interact with as though nothing
              had gone wrong. The rest of the procedure does not complete though. I
              know that with "Just My Code" enabled, it wouldn't break into the
              third party control code, but in this case the error *is* happening at
              "my code" level. It always used to break in but now it no longer does.

              I've looked into the Exceptions list under the debug menu and it is
              set to break when a user-unhandled null reference excetion happens.

              Bob

              On Jul 3, 10:29 am, RvGrah <rvgrahamsevate n...@sbcglobal. netwrote:
              I seem to have acquired a strange issue here, some of my programs are
              now failing silently, resuming without notification that anything went
              wrong, both on my development machine and (I think) on the users
              machines. For instance, I was just noticing a spot where a table
              adapter's fill method fails, and the new form just opens up anyway
              after skipping the rest of the form's Load procedure without any
              indication anything went wrong. I haven't fiddled with any of the
              debug settings, and I don't remember if this started when I upgraded
              to VS 2008 or a while later. I am pretty sure it never happened in
              2005 though.
              >
              What settings should I check or change to *make* it tell me something
              went wrong? Sorry, I know this makes me seem like a lame developer,
              it's just that the default debug settings have always worked fine for
              me so I don't know much about altering them.
              >
              Bob Graham

                Comment

                Previous template Next
                Working...