1. Exception Handling Strategies
2. Exception Handling Strategy - Overview
3. Exception Handling Requirements
4. Application Survival
5. Notifying Relevant Parties
6. Error Diagnostics and Reproduction
7. Separation of Abstraction Layers
8. More Readable and Maintainable Code
9. Error Location and Context
10. Error Causes, Types and Reactions
11. Strategy Elements
12. Error Detection
13. Error Information Gathering
14. Throwing Exceptions
15. Propagating Exceptions
16. Catching Exceptions
17. An Exception Handling Strategy Template
18. An Exception Class Template
19. Throwing the AppException
20. Propagating the AppException
21. The ErrorInfo List
22. Catching the AppException
23. Avoid Exception Hierarchies

All those try-catch-finally clauses spread out in your code makes the code harder to read. An effective exception handling strategy can eliminate some of all this boilerplate code. This is done by only handling the exceptions in the place where you can actually do something about them, and by using exception handling templates. I will get into more detail about these topics later in this tutorial.

While cleaner code is definitely nice, it is not nearly as important as keeping the application alive, and notifying the right people about errors. Skeptics may claim that with cleaner code it is easier to assure application survival, and this I cannot deny. Some of the techniques discussed in this tutorial will both make application survival easier, and clean up the code. Whether one is a byproduct of the other, or vice versa really isn't that important.