Headache about Error Handling and Debugging

[James Ma]

Now I am debugging a buggy VB.NET function like following

Function foo()
Try
‘ many loops and codes and nested try catch here!
……
Catch (ex as Exception)
Msgbox ex.message
Finally
…
end try
End function

My headache is: when it causes an exception, it’s very hard for me to locate
which line causes the error. I remember if I use the “On Error Goto
Err_Hanlder� method, I can always use a simple “Resume� statement to help me
locate the buggy line. But I heard the VB’s “On Error GoTo� is not
recommended and also remember I can only use the �try catch� in C#, C++ or
Java.

Question: Is there an easy method to achieve the same effect as the resume
(I mean for debugging purpose)? or can I set the IDE to break at the buggy
line instead of at the catch block? Is this a legitimate reason that favor
“On Error Goto� more than “Try Catch�?

Look forward your insight.
James

[Kerry Moorman]

James,

In VS 2003 you can break into the debugger when an exception is thrown.

From the Debug menu, choose Exceptions. From the Exceptions dialog select
Common Language Runtime Exceptions. Click the radio button to break into the
debugger when an exception is thrown.

Now when an exception is thrown the debugger will highlight the line causing
the exception, even though the code is within a Try Catch block.

Kerry Moorman
"James Ma" wrote:

Now I am debugging a buggy VB.NET function like following

Function foo()
Try
‘ many loops and codes and nested try catch here!
……
Catch (ex as Exception)
Msgbox ex.message
Finally
…
end try
End function

My headache is: when it causes an exception, it’s very hard for me to locate
which line causes the error. I remember if I use the “On Error Goto
Err_Hanlder� method, I can always use a simple “Resume� statement to help me
locate the buggy line. But I heard the VB’s “On Error GoTo� is not
recommended and also remember I can only use the �try catch� in C#, C++ or
Java.

Question: Is there an easy method to achieve the same effect as the resume
(I mean for debugging purpose)? or can I set the IDE to break at the buggy
line instead of at the catch block? Is this a legitimate reason that favor
“On Error Goto� more than “Try Catch�?

Look forward your insight.
James

[James Ma]

Thank you so much. It's working, though I'm using VS2005.

"Kerry Moorman" wrote:

James,

In VS 2003 you can break into the debugger when an exception is thrown.

From the Debug menu, choose Exceptions. From the Exceptions dialog select
Common Language Runtime Exceptions. Click the radio button to break into the
debugger when an exception is thrown.

Now when an exception is thrown the debugger will highlight the line causing
the exception, even though the code is within a Try Catch block.

Kerry Moorman
"James Ma" wrote:

Now I am debugging a buggy VB.NET function like following

Function foo()
Try
‘ many loops and codes and nested try catch here!
……
Catch (ex as Exception)
Msgbox ex.message
Finally
…
end try
End function

My headache is: when it causes an exception, it’s very hard for me to locate
which line causes the error. I remember if I use the “On Error Goto
Err_Hanlder� method, I can always use a simple “Resume� statement to help me
locate the buggy line. But I heard the VB’s “On Error GoTo� is not
recommended and also remember I can only use the �try catch� in C#, C++ or
Java.

Question: Is there an easy method to achieve the same effect as the resume
(I mean for debugging purpose)? or can I set the IDE to break at the buggy
line instead of at the catch block? Is this a legitimate reason that favor
“On Error Goto� more than “Try Catch�?

Look forward your insight.
James

[Jim Wooley]

> Now I am debugging a buggy VB.NET function like following

My headache is: when it causes an exception, it's very hard for me to
locate which line causes the error. I remember if I use the "On Error
Goto Err_Hanlder" method, I can always use a simple "Resume" statement
to help me locate the buggy line. But I heard the VB's "On Error GoTo"
is not recommended and also remember I can only use the "try catch" in
C#, C++ or Java.

Another alternative you can do is to add line numbers to your code and retrieve
the last successful line using the ERL() function (see http://msdn.microsoft.com/library/de...lproperty.asp).
This function has been in VB but undocumented between versions 3 and 6. It
is now documented again.

See http://devauthority.com/blogs/jwoole...12/21/661.aspx for
a sample implementation.

Jim Wooley

[Stephany Young]

And another alternative is, instead of displaying the exception message in a
message box, write the exception itself to the console:

Console.Writeline(ex.ToString())

This will give you the stack trace which in turn will show you the name of
the source file and the line number along with the procedure name.
"James Ma" <Ja*****@discussions.microsoft.com> wrote in message
news:AA**********************************@microsof t.com...

Now I am debugging a buggy VB.NET function like following

Function foo()
Try
‘ many loops and codes and nested try catch here!
……
Catch (ex as Exception)
Msgbox ex.message
Finally
…
end try
End function

My headache is: when it causes an exception, it’s very hard for me to
locate
which line causes the error. I remember if I use the “On Error Goto
Err_Hanlder” method, I can always use a simple “Resume” statement to help
me
locate the buggy line. But I heard the VB’s “On Error GoTo” is not
recommended and also remember I can only use the ”try catch” in C#, C++ or
Java.

Question: Is there an easy method to achieve the same effect as the resume
(I mean for debugging purpose)? or can I set the IDE to break at the buggy
line instead of at the catch block? Is this a legitimate reason that favor
“On Error Goto” more than “Try Catch”?

Look forward your insight.
James

[CMM]

Wow! Thanks! This is truly an amazing tip.
I love MS.

--
-C. Moya
www.cmoya.com