Response.End() behavior change in ASP.NET 2.0

Posted by: Rick Strahls WebLog, on 04 Nov 2005 | View original

 Here’s a cool new behavior in ASP.NET 2.0: Response.End() no longer kills post Application events! In 1.1 if you called Response.End() ASP.NET effectively bypassed the rest of the event pipeline which would cause problems for any content modifying modules or Application level event hooks. In 2.0 post Handler events continue to fire.   I think this is the way it should work, but some people may find this change will break their existing applications if they relied on Response.End()...

Advertisement

Similar Posts

  • Tip/Trick: Show Detailed ASP.NET Error Messages to Developers (and only to Developers) more
  • Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack more
  • Blogging from Tech Ed 2006 - Stefan Shakow on ASP.NET - level 400 more
  • Throughput and Latency Considerations more
  • Blogging from Tech Ed 2006 - Stefan Shakow on ASP.NET - level 400 more
  • Gridview Export to Excel more
  • Templates - Part 1 more
  • Dynamic Themes assignment more
  • Hosting Microsoft Live.com Gadgets in your ASP.NET Application more
  • Tech Ed 2006 Summary more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD