More Elegant Exception Handling Than Multiple Catch Blocks? [duplicate]

by

In my opinion, a bunch of “ugly” catch blocks IS the best way to handle that situation.

The reason I prefer this is that it is very explicit. You are explicitly stating which exceptions you want to handle, and how they should be handled. Other forms of trying to merge handling into more concise forms lose readability in most cases.

My advice would be to stick to this, and handle the exceptions you wish to handle explicitly, each in their own catch block.

More Related Contents:

  1. Catch multiple exceptions at once?
  2. How to handle AccessViolationException
  3. How slow are .NET exceptions?
  4. Cannot delete directory with Directory.Delete(path, true)
  5. Best practices for exception management in Java or C# [closed]
  6. What is the proper way to rethrow an exception in C#? [duplicate]
  7. Avoiding first chance exception messages when the exception is safely handled
  8. .NET – What’s the best way to implement a “catch all exceptions handler”
  9. Troubleshooting BadImageFormatException
  10. Does a locked object stay locked if an exception occurs inside it?
  11. Active Directory COM Exception – An operations error occurred (0x80072020)
  12. Why does a bad password cause “Padding is invalid and cannot be removed”?
  13. How to avoid a System.Runtime.InteropServices.COMException?
  14. Image.FromStream() method returns Invalid Argument exception
  15. Read Big TXT File, Out of Memory Exception
  16. Best practices: throwing exceptions from properties
  17. How to prevent an exception in a background thread from terminating an application?
  18. Show line number in exception handling
  19. How to serialize an Exception object in C#?
  20. ArgumentOutOfRangeException on initialized List
  21. How can I handle forms authentication timeout exceptions in ASP.NET?
  22. Exception.Message vs Exception.ToString()
  23. Is there a built in .NET exception that indicates an illegal object state?
  24. How can I determine which exceptions can be thrown by a given method?
  25. In a .net Exception how to get a stacktrace with argument values
  26. Which exceptions shouldn’t I catch?
  27. Asp.net mvc override OnException in base controller keeps propagating to Application_Error
  28. The ObjectContext instance has been disposed and can no longer be used for operations that require a connection [duplicate]
  29. Could not load file or assembly ‘System.Windows.Interactivity’ [duplicate]
  30. Which types of exception not to catch?

Leave a Comment