What makes a method non-debuggable?

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

    What makes a method non-debuggable?

    I got a few classes generated by a tool (wsdl.exe) that are somehow 'hidden' from step-by-step debugging. I've added some methods to the classes, and would like to be able to step through them, but the debugger steps over the methods. Why is this happening?

    Gustaf
    Tags: None
    • Marc Gravell
      #2
      Re: What makes a method non-debuggable?

      I believe wsdl.exe adds [DebuggerStepThr ough] or
      [System.Diagnost ics.DebuggerSte pThroughAttribu te] to the methods it
      writes - if present, that would be the offender. IIRC, other similar
      attributes exist. Look at the class file generated and see what it
      has.

      Marc


        Comment

        • Ignacio Machin \( .NET/ C# MVP \)
          #3
          Re: What makes a method non-debuggable?

          Hi,

          "Gustaf" <gustafl@algone t.sewrote in message
          news:eSkM3nB2HH A.5980@TK2MSFTN GP04.phx.gbl...
          >I got a few classes generated by a tool (wsdl.exe) that are somehow
          >'hidden' from step-by-step debugging. I've added some methods to the
          >classes, and would like to be able to step through them, but the debugger
          >steps over the methods. Why is this happening?

          In addition to Mark's comments, check that the debug info exist for those
          types.


            Comment

            Previous template Next
            Working...