krisbrixon
Programmer
Does anyone have any tips/resources/code/... for handling error messages beyond the simple messagebox.
My goal is to throw the error all the way up to the GUI class (I can do that) and then gather as much debugging/environemnt information as possible and write to a file or something.
A little background info:
Our old program (written in Clipper) when you got an error it would show the last 20 function calls and what line it was on. This allowed us to pinpoint where the customer received the error and show the path to the error message. I would love to do something like this (or better) in VB.NET.
On the following page you can see some functions I found dealing with error handling, but they are not much more than the simple messagebox error messages.
Any tips / resources / code / articles / .... that are beyond the simple error handling you see in all the books would be greatly appreciated!!
Kris
![[ponder] [ponder] [ponder]](/data/assets/smilies/ponder.gif)
My goal is to throw the error all the way up to the GUI class (I can do that) and then gather as much debugging/environemnt information as possible and write to a file or something.
A little background info:
Our old program (written in Clipper) when you got an error it would show the last 20 function calls and what line it was on. This allowed us to pinpoint where the customer received the error and show the path to the error message. I would love to do something like this (or better) in VB.NET.
On the following page you can see some functions I found dealing with error handling, but they are not much more than the simple messagebox error messages.
Any tips / resources / code / articles / .... that are beyond the simple error handling you see in all the books would be greatly appreciated!!
Kris
![[ponder] [ponder] [ponder]](/data/assets/smilies/ponder.gif)