What makes a method non-debuggable?

  • Thread starter Thread starter Gustaf
  • Start date Start date
G

Gustaf

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
 
I believe wsdl.exe adds [DebuggerStepThrough] or
[System.Diagnostics.DebuggerStepThroughAttribute] 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
 
Hi,

Gustaf said:
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?
Click to expand...


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