Did you know that … (Response.End versus HttpContext.Current.ApplicationInstance.CompleteRequest)

If you use the Response.End, Response.Redirect, or Server.Transfer method, a ThreadAbortException exception occurs. You can use a try-catch statement to catch this exception (of type ThreadAbortException) but having an empty catch block after my Response.End was kinda ugly.

 

So, rather than doing Response.End, we can call HttpContext.Current.ApplicationInstance.CompleteRequest it will causes ASP.NET to bypass all events and filtering in the HTTP pipeline chain of execution and directly execute the EndRequest event…

http://msdn.microsoft.com/en-us/library/system.web.httpapplication.completerequest%28vs.80%29.aspx

We never stop learning !