ASP.Net: Server.Transfer() and "Thread was being aborted."

I recently ran into something that was beginning to ruin my day. Check out the following snippet of ASP.Net code:

private void Page_Load(object sender, System.EvenArgs e)
{
   try
   {
      // (Do some stuff, then ... )
      Server.Transfer("AnotherPage.aspx");
   }
   catch (Exception ex)
   {
      throw new Exception(ex.Message, ex);
   }
}

Looks innocent, right? Wrong!

Here's what's wrong. When the Server.Transer() is executed, the catch clause catches the following exception: "Thread was being aborted." And if you have a custom error page it will catch that exception every time you do a Server.Transfer().

One suggestion, which worked for me, is to use Server.Execute() instead of Server.Transfer(). The main difference is that Server.Transfer() terminates execution of the current page (which is what causes the exception), and Server.Execute() executes the specified page and then returns control to the current page, much like a function call. There are other differences, but I'm not going to get into them here. Suffice to say, that Server.Execute() won't cause the "Thread was being aborted" exception to be thrown.

Cheers.