[In addition to the error] The "Abort thread" error generated by response. Redirect

In the past two days, exceptions of threadabortexception will always appear during development and debugging. The exception is caused by response. although the Redirect method produces a thread problem, I don't know why redirect has such an error. I haven't encountered it before. I just encountered it when I transferred it to Asp.net 2.0 for development. After a click on Google, Ms discovered this problem long ago, but provided a solution. The following is a summary of the main information: Response. End , Response. Redirect Or Server. Transfer Method. Threadabortexception Exception. You can use Try-catch Statement to capture this exception. Cause Response. End Method termination page execution, and switch this execution to the application Program In the event Pipeline Application_endrequest Event. Do not execute Response. End The Code Line.

This problem occurs inResponse. RedirectAndServer. TransferMethod, because both methods are called internallyResponse. End. To solve this problem, use one of the following methods:

•

ForResponse. End, CallHttpcontext. Current. applicationinstance. completerequestMethod insteadResponse. EndTo skipApplication_endrequestEvent code execution.

•

ForResponse. Redirect, Use overloadResponse. Redirect (string URL, bool endresponse).EndresponseParameter transferFalseTo cancelResponse. End. Example: response. Redirect ("nextpage. aspx", false ); B-e-a-utiful! This is simple. The problem is solved. Thank you, Microsoft, Google, and God! Now I have posted the solution to help more people solve similar problems encountered during the development process. I will search for the solution to the end!