Response. End Method
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Sends all currently buffered output to the client, stops execution of the page, and raises the EndRequest event.
public: void End();
public void End ();
member this.End : unit -> unit
Public Sub End ()
The call to End() has terminated the current request.
This method is provided only for compatibility with ASP - that is, for compatibility with COM-based Web-programming technology that preceded ASP.NET. If you want to jump ahead to the EndRequest event and send a response to the client, it is usually preferable to call CompleteRequest instead.
To mimic the behavior of the
End method in ASP, this method tries to raise a ThreadAbortException exception. If this attempt is successful, the calling thread will be aborted, which is detrimental to your site's performance. In that case, no code after the call to the End method is executed.
If the End method is not able to raise a ThreadAbortException, it instead flushes the response bytes to the client. It does this synchronously, which can also be detrimental to your site's performance.
In either case (whether or not a ThreadAbortException exception is successfully raised), the response pipeline jumps ahead to the EndRequest event.
The CompleteRequest method does not raise an exception, and code after the call to the CompleteRequest method might be executed. If your intention is to avoid execution of subsequent code, and if the performance penalty of End is acceptable, you can call End instead of CompleteRequest.