Use custom exceptions to add information that will be more meaningful to your users when exceptions occur. And, you still can maintain all the information from the original exception.
Handling exceptions can sometimes be a little tricky. If you are not careful, your code may act on the wrong information. Learn how to bubble up exceptions while keeping the original exception information intact.
Be a good resource citizen by implementing IDisposable. You will be able to ensure that your objects have the opportunity to release all of their managed and unmanaged resources.
Take control of the lifetime of your objects. Release your object's resources on your schedule, not when the CLR determines they are no longer needed.
Learn about the techniques and guidelines you can use to make your application stable and less prone to errors, hande errors in a graceful manner, and avoid crashing.
Learn about the risks of an exception being thrown where it is generally not expected, and ways to prevent some insidious errors.
Although the .NET Framework provides many standard exceptions, you also can create, throw, and catch your own custom exceptions. In fact, custom exception types are a powerful feature of the VB .NET language.
Garbage collection does not determine when resources are collected, so it's up to you to protect classes that use finite resources that need some deterministic cleanup. Learn how the using block—a shorthand version of the try-finally block—enables you to do so.
This month, .NET Nuts & Bolts covers exception handling, examining what exceptions are and why they are important. You'll learn how to use them, how to create custom exceptions, and how to apply common best practices.
One often-overlooked ability of .NET is that you can create a custom exception handler that will allow you to catch all unhandled exceptions thrown during the execution of your application.
Your applications can end sadly and abruptly. While that's fine during development, you don't want to have your applications die with an exception in front of our users. Nothing is more embarrassing than a confusing dialog or web page referring to unhandled exceptions.
