Question

After running into some un-handled exceptions when using Response.Redirect(), I read it up, and it appears several people are recommending to use ApplicationInstance.CompleteRequest() instead, to avoid an unhandled ThreadAbortException for each redirect, and thereby avoiding a performance hit. But let’s say you catch that exception instead like below…

try
{
    response.Redirect("Default.aspx", false);
    response.End();
}
catch (ThreadAbortException)
{
    // Do nothing
}

Will this remove the hit on performance when the exception is now swallowed?

Answer 1

The exception is still being thrown, so all of the overhead of generating the exception and catching it is still present.