Page 29 : 30
Object-oriented Programming in C#
Exception Handling
* Fundamental Questions about Exception Handling
What is the motivation?
What is an error?
What is normal? What is exceptional?
Examples of normal and exceptional aspects
When are errors detected?
How are errors handled?
Where are errors handled?
* Conventional Exception Handling
Exception Handling Approaches
Mixing normal and exceptional cases
* Object-oriented Exception Handling
Errors as Objects
Classification of Errors
* Exceptions and Exception Handling in C#
Exceptions in a C# program
The try-catch statement C#
Handling exceptions in C#
The hierarchy of exceptions in C#
The class System.Exception in C#
Handling more than one type of exception in C#
Propagation of exceptions in C#
Raising and throwing exceptions in C#
Try-catch with a finally clause
Rethrowing an exception
Raising an exception in an exception handler
Comparison with exception handling in Java
* Recommendations about exception handling
Recommendations about exception handling
Recommendations about exception handling
Recommendations about exception handling
Control flow
Do not use throw and try-catch as iterative or conditional control structures
Normal control flow should be done with normal control structures
Efficiency
It is time consuming to throw an exception
It is more efficient to deal with the problem as a normal program aspect - if possible
Naming
Suffix names of exception classes with "
Exception
"
Exception class hierarchy
Your own exception classes should be subclasses of
ApplicationException
Or alternatively (as of a more recent recommendation) of
Exception
.
Best practices for handling exceptions (MSDN)