When to use try/catch blocks?

by

The basic rule of thumb for catching exceptions is to catch exceptions if and only if you have a meaningful way of handling them.

Don’t catch an exception if you’re only going to log the exception and throw it up the stack. It serves no meaning and clutters code.

Do catch an exception when you are expecting a failure in a specific part of your code, and if you have a fallback for it.

Of course you always have the case of checked exceptions which require you to use try/catch blocks, in which case you have no other choice. Even with a checked exception, make sure you log properly and handle as cleanly as possible.

More Related Contents:

  1. Will code in a Finally statement fire if I return a value in a Try block?
  2. Why is try {…} finally {…} good; try {…} catch{} bad?
  3. Is there a difference between “throw” and “throw ex”?
  4. WPF global exception handler [duplicate]
  5. Best practices for catching and re-throwing .NET exceptions
  6. Why catch and rethrow an exception in C#?
  7. How using try catch for exception handling is best practice
  8. .NET Global exception handler in console application
  9. .NET – What’s the best way to implement a “catch all exceptions handler”
  10. Main method code entirely inside try/catch: Is it bad practice?
  11. What’s the difference between Application.ThreadException and AppDomain.CurrentDomain.UnhandledException?
  12. What is the real overhead of try/catch in C#?
  13. Handling exceptions, is this a good way?
  14. The calling thread cannot access this object because a different thread owns it [duplicate]
  15. How can I catch a 404?
  16. Try-catch speeding up my code?
  17. Wrong line number on stack trace
  18. How to catch ALL exceptions/crashes in a .NET app [duplicate]
  19. How to check if IOException is Not-Enough-Disk-Space-Exception type?
  20. Is this a bad practice to catch a non-specific exception such as System.Exception? Why?
  21. What is ApplicationException for in .NET?
  22. Show line number in exception handling
  23. What really happens in a try { return x; } finally { x = null; } statement?
  24. How to log all thrown exceptions?
  25. How to use the Paint event to draw shapes at mouse coordinates
  26. Properly draw text using GraphicsPath
  27. Nullable vs. int? – Is there any difference?
  28. Uncompressing gzip response from WebClient
  29. How to compare Unicode characters that “look alike”?
  30. Does Func.BeginInvoke use the ThreadPool?

Leave a Comment