.NET Tip: Throwing Custom Exceptions

Creating your own custom exceptions is very easy and allows your code to be more explicit as well as being able to provide more user-friendly error messages. To show how to use custom exceptions, I will use connecting to a database as an example. Connecting to a database is something your application probably does on a regular basis and is a common point of failure. The first step is to create the class for your custom exception that inherits from another exception class. In this case, you'll create an UnableToOpenDatabaseException based on the Exception class. Here is what the custom exception class looks like:

public class UnableToOpenDatabaseException : Exception
{
   public UnableToOpenDatabaseException()
      : base()
   {
   }

   public UnableToOpenDatabaseException(string Message)
      : base(Message)
   {
   }

   public UnableToOpenDatabaseException(string Message,
                                        Exception InnerException)
      : base(Message, InnerException)
   {
   }

   protected UnableToOpenDatabaseException(SerializationInfo Info,
                                           StreamingContext Context)
      : base(Info, Context)
   {
   }
}

To use the custom exception, you need to check to see whether an exception is thrown when you attempt to connect to the database. In my case, I'm connecting to SQLServer, so I will check to see if a SQLException was thrown. If a SQLException is thrown, I throw the new UnableToOpenDatabaseException, passing the original exception to the new one. If an exception other than a SQLException is thrown, I simply rethrow the original exception.

using (SqlConnection CN =
   new SqlConnection("*** Your connection string here ***"))
{
   try
   {
      CN.Open();
   }
   catch (SqlException ex)
   {
      // Throw the custom UnableToOpenDatabaseException
      throw new UnableToOpenDatabaseException("Unable to open
         database connection.", ex);
   }
   catch (Exception ex)
   {
      // Rethrow the original exception
      throw;
   }
}

This allows the calling code to take advantage of the new exception while still allowing it to access all of the original exception information if needed. This example lumped any type of SQLException under the new exception type. If you needed more granularity in your exceptions, you could create custom exceptions for different failure conditions.

About the Author

Jay Miller is a Software Engineer with Electronic Tracking Systems, a company dedicated to robbery prevention, apprehension, and recovery based in Carrollton, Texas. Jay has been working with .NET since the release of the first beta and is co-author of Learn Microsoft Visual Basic.Net In a Weekend. Jay can be reached via email at jmiller@sm-ets.com.



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Live Event Date: December 11, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT Market pressures to move more quickly and develop innovative applications are forcing organizations to rethink how they develop and release applications. The combination of public clouds and physical back-end infrastructures are a means to get applications out faster. However, these hybrid solutions complicate DevOps adoption, with application delivery pipelines that span across complex hybrid cloud and non-cloud environments. Check out this …

  • On-demand Event Event Date: October 29, 2014 It's well understood how critical version control is for code. However, its importance to DevOps isn't always recognized. The 2014 DevOps Survey of Practice shows that one of the key predictors of DevOps success is putting all production environment artifacts into version control. In this webcast, Gene Kim discusses these survey findings and shares woeful tales of artifact management gone wrong! Gene also shares examples of how high-performing DevOps …

Most Popular Programming Stories

More for Developers

RSS Feeds