I must admit, in the past when I just want some code to run, but it's not critical if it fails, I have written a try catch block which looks like this:

try
{
   RecordPageView(pageId);
}
catch
{
   //Do nothing
}

I feel really guilty for it, and I know there must be something better than just leaving a comment.

Sometimes I will log the error using log4net in case I need to check them later:

using log4net;
using System.Reflection;

ILog Log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);

try
{
   RecordPageView(pageId);
}
catch(Exception ex)
{ 
   Log.Error("Unable to record page view", ex); 
}

You don't have to have a catch, you can do just a try finally like this:

using System.Data.SqlClient;

SqlConnection databaseConnection = GetDatabaseConnection("connectionName");
databaseConnection.Open();

try
{
   RecordPageView(pageId, databaseConnection);
}
finally
{
   databaseConnection.Close();
}

The finally block is very useful because it will run every time even after an exception.
This is useful for closing connections.

And of course you can use try catch and finally

using log4net;
using System.Reflection;
using System.Data.SqlClient;

ILog Log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);
SqlConnection databaseConnection = GetDatabaseConnection("connectionName");
databaseConnection.Open();

try
{
   RecordPageView(pageId, databaseConnection);
}
catch (Exception ex)
{
   Log.Error("Unable to record page view", ex);
}
finally
{
   databaseConnection.Dispose();
}

How do you use try catch blocks?

If you would like to learn more about exception handling why not use your free 10 day trial on Pluralsight to go through the Enterprise Library Exception Handling Application Block