title: Exception Handling
body: <p>Is Structured Exception Handling bad? What is the right way to handle exceptions?</p>
  
  <p><strong>EDIT: Exception Handling in .NET using C#.</strong></p>
  
  <p>I usually have a set of specific exception classes (DivideByZeroException, ArrayTypeMismatchException) and don't have a generic "catch (Exception ex)".</p>
  
  <p>The thinking behind this is that I expect certain types of exceptions to occur and have specific actions defined when they occur and the unexpected exceptions would rise up the the interface (either windows or web). Is this a good practice? </p>