Figuring the error source of an Exception

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

Hello,

I'm a little green in this area, so any suggested reading or examples is
appreciated.

In my release version of managed code, is there a way to know what command
caused an exception?

I know the message and source of the exception using the exception object.
Is there a way to get the IL offset, so I know which command caused the
exception?

Thanks,

Eric
 
Stack Trace.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Who is Mighty Abbott?
A twin turret scalawag.
 
With a debug assembly you see the line number.

With the release code all you get is the function name, nothing else. How
can I get the IL offeset?
 
Back
Top