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

Posted by: Rick Strahls WebLog, on 04 Nov 2005 | View original | NEW Bookmarked: 0 time(s)

 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
Category: ASP.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 4621 | Hits: 484

Similar Posts

  • Announcing the Microsoft AJAX CDN more
  • Application Identifiers (AI) for EAN-128 barcode generation more
  • No JavaScript IntelliSense in VS 2010 Beta 2? Reset your Settings more
  • Dovetail is Hiring a Junior-to-Mid-level .NET Developer more
  • ASP.NET disk-based caching more
  • Why VBA Still Makes Sense more
  • Trials & Tribulations of running windows scripts in Vista more
  • Speaking at the Portland Area .NET User Group on Tuesday Sept 1st more
  • Hey, nice package! more
  • Hey, nice package! more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | 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