Post 1 of 6

Error Trapping

234 Views, 5 Replies
03-14-2012 01:16 PM

In VB6 I used to use

On Error GoTo My_Error
   On Error GoTo 0
   Exit Sub
    MsgBox "Error " & Err.Number & " (" & Err.Description & ") on line " & Erl & " in procedure MyProcedure of Module MyModule"


By using this in VB.net it the error is skipped and it jumps to the error routine. Easily added using MZ tools.

The same code doesn't report what line but at least reports an error.


 Using the Try, Catch & Finally method often just crates a fatal error and I have to step through code trying to work out what the problem is.


A big problem is that I have spent a long time creating an application with several reactors. I'm not sure if I will ever figure out why it is creating fatal errors.


Is there some reading material that can help me trap errors or work out if I have not disposed of something that should have been?


Re: Error Trapping

03-14-2012 01:40 PM in reply to: SRSDS

I've had some fatal errors from using Try/Catch ex as Exception/End Try as well.  However I was able to trap them using the following:



'error message

End Try.


It obviously doesn't provide you with an exception that you can then report to your user, but you should be able to figure out what the error is while debugging and then tell your code to catch it.



Post 3 of 6

Re: Error Trapping

03-14-2012 01:49 PM in reply to: SRSDS



This link may help you to understand exceptions: http://msdn.microsoft.com/en-us/library/5b2yeyab(v=vs.100).aspx


Gaston Nunez

Post 4 of 6

Re: Error Trapping

03-14-2012 01:52 PM in reply to: SRSDS

Try in the Visual studio to go to Project --> Properties-->Compile Tab

and set Option Strict to On, then hit F5, you will be see many possible

bad lines in your code before you run it, then revert back Option Stict to Off

and run again

Maybe it will be usefull for you



Post 5 of 6

Re: Error Trapping

03-15-2012 09:00 AM in reply to: Hallex

It most often never makes it to the catch part . The fatal error is initiated on the bad bit of code.

Something I will have to accept it seems.


That option strict generates a mass of errors. I'll see if I can spot anything unusual there.

Thanks all.

Post 6 of 6

Re: Error Trapping

03-15-2012 09:59 AM in reply to: SRSDS

If you're importing Autodesk.AutoCAD.Runtime and you do a "Catch ex as exception" you're only catching the Autodesk.AutoCAD.Runtime exceptions so if you get a System.Exception it will error and not hit the catch.


The Runtime.exception inherits System.exception so catching System.exceptions should get them all.

Post to the Community

Have questions about Autodesk products? Ask the community.

New Post