Q&A
Q1: | When I upgrade my Visual Basic 6 application to Visual Basic .NET, can I still use my On Error Goto error-handling routines? |
A1: | Yes, you can. However, they're provided for backward compatibility only, so you should consider rewriting your error-handling routines to the new structured exception handling in .NET. |
Q2: | I'm used to Visual Basic 6 debugging, and I like to change my code while I am in debug mode. Why does .NET make me restart every time I do that now? |
A2: | Visual Basic .NET is a compiled language, not interpreted. That means in order for your code to run, the intermediate language must be compiled before it runseven when you're debugging. So, if you make a change to your code, you must restart the application to re-create the intermediate language code. |
Q3: | Exceptions are cool. I like the fact that I help out the user by letting him know what happened. Is there a way I can create my own custom exceptions? |
A3: | Yes. If you're writing classes and you want to create custom errors that are raised back to the user, you can inherit from the Exception class. |