If you use the Response.End
method, a ThreadAbortException
exception occurs. You can use a try-catch
statement to catch this exception.
method ends the page execution and shifts the execution to the Application_EndRequest
event in the application's event pipeline. The line of code that follows Response.End
is not executed.
This problem occurs in the Response.Redirect
methods because both methods call Response.End
To work around this problem, use one of the following methods:
- For Response.End, call the HttpContext.Current.ApplicationInstance.CompleteRequest method instead of Response.End to bypass the code execution to the Application_EndRequest event.
- For Response.Redirect, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. For example:
If you use this workaround, the code that follows Response.Redirect is executed.
Response.Redirect ("nextpage.aspx", false);
- For Server.Transfer, use the Server.Execute method instead.
This behavior is by design.
Article ID: 312629 - Last Review: August 30, 2012 - Revision: 4.0
- Microsoft ASP.NET 4.5
- Microsoft ASP.NET 4
- Microsoft ASP.NET 3.5
- Microsoft ASP.NET 2.0
- Microsoft ASP.NET 1.1
- Microsoft ASP.NET 1.0
|kbexcepthandling kbprb KB312629|