Calling Response.End may cause lifecycle events to be supressed

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

If you invoke Reponse.End directly or via Response.Redirect, any page or application lifecycle events would normally be raised before the HttpApplication.EndRequest Event will bypassed.� If you have code that handles any of the bypassed events, you may need add an EndRequest event handler to insure that your code will run in cases where Response.End is invoked.

If you choose to implement a Response.End event handler, note that it will be called on every response in addition to your other application event handlers so you must exercise care that it does not interfere with your� normal event handler.



Page lifecycle events are discussed in:

http://msdn.microsoft.com/en-us/library/system.web.ui.page_events.aspx

�

Application life cycle events are enumerated for IIS 5 and 6 in:

http://msdn.microsoft.com/en-us/library/ms178473.aspx

�

Application life cycle events are enumerated for IIS 7� in:

http://msdn.microsoft.com/en-us/library/bb470252.aspx

�