I am working through some intricate code and I want to make sure I am made aware of any errors that may pop up at run-time.  How I have done this in the past is to create a class that I throw exceptions at and from there send emails or alerts to let me know what is going on.  As I understand it there is some exception handling that is already going on within the framework via an error provider.  How do I take advantage of that and still provide a streamlined way of handling my exceptions?  Also, is this a proper approach to using transactions within my code?

Here is an example of my code that I am trying to work this through:

private void cmdTransfers_Click(object sender, EventArgs e)
{
    try
    {
        // Wrap this entire process in a transaction
        BusinessLayer.TransactionBegin("MyDataSourceName", IsolationLevel.ReadCommitted);

        // Retrieve the next [snip] . . . lots of stuff happening here . . .

       MyLastProcedureToRun(myParm);

        BusinessLayer.TransactionCommit("MyDataSourceName");
    }
    catch (Exception ex)
    {
        // place cool SF exception handling here, if any

        // this is my current way of doing it
        SPXExceptionHandler.ReportException(ex);  // exceptions are logged, emailed, etc.
        BusinessLayer.TransactionRollback("Dynamics");
    }
}

Thanks!
Bill