Wierd .NET Debugging behavior...

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

    Wierd .NET Debugging behavior...

    We are experiencing some wierd debugging behavior. What happens is
    that, during debugging with VS 2003, the debugger seems to 'skip'
    statements that are associated with database operations. For instance,
    I can be single-stepping through a VB.NET program, and once I hit a DB
    related statement (such as setting command parameters, executing a data
    reader, etc) the debugger will simply 'skip' ahead a number of
    statements (if not all the way to the end unless a breakpoint has been
    assigned before this). The code it 'skips' actually runs - it just no
    longer single-steps through it. This only occurs with DB related
    statements, and it is NOT consistant (i.e. some statements it single
    steps through fine, others it exhibit this skipping issue). I know it
    is not my machine because others in our group have experienced the same
    thing.

    Now, we use Oracle and recently installed the Oracle 10g ODP client,
    and that is when this wierd issue began. So it may be an ODP issue, but
    I thought I would start with one of the .NET newsgroups first. Any
    ideas? Thanks in advance.

    Chimp (Tom)

    --

    Tags: None
    • Cor Ligthert [MVP]
      #2
      Re: Wierd .NET Debugging behavior...

      Tom,

      Often helps in this to empty the generated code in the debug folder and
      start again.

      I hope this helps,

      Cor

      "Tom" <tom@nospam.com > schreef in bericht
      news:uyoT3wqfGH A.764@TK2MSFTNG P03.phx.gbl...[color=blue]
      > We are experiencing some wierd debugging behavior. What happens is
      > that, during debugging with VS 2003, the debugger seems to 'skip'
      > statements that are associated with database operations. For instance,
      > I can be single-stepping through a VB.NET program, and once I hit a DB
      > related statement (such as setting command parameters, executing a data
      > reader, etc) the debugger will simply 'skip' ahead a number of
      > statements (if not all the way to the end unless a breakpoint has been
      > assigned before this). The code it 'skips' actually runs - it just no
      > longer single-steps through it. This only occurs with DB related
      > statements, and it is NOT consistant (i.e. some statements it single
      > steps through fine, others it exhibit this skipping issue). I know it
      > is not my machine because others in our group have experienced the same
      > thing.
      >
      > Now, we use Oracle and recently installed the Oracle 10g ODP client,
      > and that is when this wierd issue began. So it may be an ODP issue, but
      > I thought I would start with one of the .NET newsgroups first. Any
      > ideas? Thanks in advance.
      >
      > Chimp (Tom)
      >
      > --
      >[/color]


        Comment

        • Tom
          #3
          Re: Wierd .NET Debugging behavior...

          Cor: I tried this but unfortunately it didn't seem to help. Even tried
          another suggestion and removed then re-added the reference to Oracle
          ODP - still no luck. And it isn't just me - others have experienced the
          same issue at my workplace.

          Any other ideas?

          Tom

          --

          Cor Ligthert [MVP] wrote:
          [color=blue]
          > Tom,
          >
          > Often helps in this to empty the generated code in the debug folder
          > and start again.
          >
          > I hope this helps,
          >
          > Cor
          >
          > "Tom" <tom@nospam.com > schreef in bericht
          > news:uyoT3wqfGH A.764@TK2MSFTNG P03.phx.gbl...[color=green]
          > > We are experiencing some wierd debugging behavior. What happens is
          > > that, during debugging with VS 2003, the debugger seems to 'skip'
          > > statements that are associated with database operations. For
          > > instance, I can be single-stepping through a VB.NET program, and
          > > once I hit a DB related statement (such as setting command
          > > parameters, executing a data reader, etc) the debugger will simply
          > > 'skip' ahead a number of statements (if not all the way to the end
          > > unless a breakpoint has been assigned before this). The code it
          > > 'skips' actually runs - it just no longer single-steps through it.
          > > This only occurs with DB related statements, and it is NOT
          > > consistant (i.e. some statements it single steps through fine,
          > > others it exhibit this skipping issue). I know it is not my machine
          > > because others in our group have experienced the same thing.
          > >
          > > Now, we use Oracle and recently installed the Oracle 10g ODP client,
          > > and that is when this wierd issue began. So it may be an ODP issue,
          > > but I thought I would start with one of the .NET newsgroups first.
          > > Any ideas? Thanks in advance.
          > >
          > > Chimp (Tom)
          > >
          > > --[/color][/color]



          --

            Comment

            • Cor Ligthert [MVP]
              #4
              Re: Wierd .NET Debugging behavior...

              Tom,

              Never did this with ASPNET. If an not catched error is thrown, than in my
              idea the program is stopped and goes on with the browser.

              Can you try to change while your application is loaded using the Debug menu
              the exceptions.
              You can set them in a lot of ways, and even very selective, even can you
              tell to pass those.

              Cor

              "Tom" <tom@nospam.com > schreef in bericht
              news:%23JnCj3Oi GHA.1508@TK2MSF TNGP04.phx.gbl. ..[color=blue]
              > Cor: I tried this but unfortunately it didn't seem to help. Even tried
              > another suggestion and removed then re-added the reference to Oracle
              > ODP - still no luck. And it isn't just me - others have experienced the
              > same issue at my workplace.
              >
              > Any other ideas?
              >
              > Tom
              >
              > --
              >
              > Cor Ligthert [MVP] wrote:
              >[color=green]
              >> Tom,
              >>
              >> Often helps in this to empty the generated code in the debug folder
              >> and start again.
              >>
              >> I hope this helps,
              >>
              >> Cor
              >>
              >> "Tom" <tom@nospam.com > schreef in bericht
              >> news:uyoT3wqfGH A.764@TK2MSFTNG P03.phx.gbl...[color=darkred]
              >> > We are experiencing some wierd debugging behavior. What happens is
              >> > that, during debugging with VS 2003, the debugger seems to 'skip'
              >> > statements that are associated with database operations. For
              >> > instance, I can be single-stepping through a VB.NET program, and
              >> > once I hit a DB related statement (such as setting command
              >> > parameters, executing a data reader, etc) the debugger will simply
              >> > 'skip' ahead a number of statements (if not all the way to the end
              >> > unless a breakpoint has been assigned before this). The code it
              >> > 'skips' actually runs - it just no longer single-steps through it.
              >> > This only occurs with DB related statements, and it is NOT
              >> > consistant (i.e. some statements it single steps through fine,
              >> > others it exhibit this skipping issue). I know it is not my machine
              >> > because others in our group have experienced the same thing.
              >> >
              >> > Now, we use Oracle and recently installed the Oracle 10g ODP client,
              >> > and that is when this wierd issue began. So it may be an ODP issue,
              >> > but I thought I would start with one of the .NET newsgroups first.
              >> > Any ideas? Thanks in advance.
              >> >
              >> > Chimp (Tom)
              >> >
              >> > --[/color][/color]
              >
              >
              >
              > --
              >[/color]


                Comment

                Previous template Next
                Working...