C#

private void DoSomething()
{
  SqlConnection connection = null;
  try
  {
    connection = new SqlConnection();
    // Do something that might cause an exception...
    connection.Open();
  }
  catch  
  {
    MessageBox.Show("Connecting to the database failed..");
  }

  if (connection.ConnectionState == ConnectionState.Open)
    connection.Close();
}

private void DoSomething()
{
  SqlConnection connection = null;
  try
  {
    connection = new SqlConnection();
    // Do something that might cause an exception...
    connection.Open();
  }
  catch(SqlException ex)  
  {
    MessageBox.Show(ex.ToString(); // or something else to notify the customer
  }
  finally
  {
    if (connection.ConnectionState == ConnectionState.Open)
      connection.Close();
  }
}

BobJanova wrote:

you (the developer) want that information to fix it

J4amieC wrote:

This is what the Windows Event Log (or, perhaps another type of log) is for.

// or show something else..

J4amieC wrote:

If your UI code is mixed with your database access code; you're doing it
wrong
 
If you show Exception messages unsanitized to your users;
you're doing it wrong

Private Sub ExceptionMethod()
    Try
        DoExceptionCode()
    Finally
        DoCleanup()
    End Try
End Sub

Private Sub ExceptionHandlerCode()
    Try
        ExceptionMethod()
    Catch ex As Exception
        ExceptionHandlerHere()
    End Try
End Sub

DragonLord66 wrote:

I had a vb editor open

connection = new SqlConnection();

try {
 doStuff();
} catch {
 throw;
}

PIEBALDconsult wrote:

If the catch in the outer try/catch actually does something (like log the Exception), then the inner try/finally should be removed and the finally moved out to make the try/catch into a try/catch/finally.

Luc Pattyn wrote:

exceptions thrown by the finally block itself.