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

Posted by: Rick Strahls WebLog, on 04 Nov 2005 | View original | 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: 6188 | Hits: 953

Similar Posts

  • jQuery UI Datepicker and z-Index more
  • Dont Repeat Yourself more
  • Add Reference Dialog Improvements (VS 2010 and .NET 4.0 Series) more
  • Behaviors vs Subclassing in Silverlight more
  • 8 techniques to find problems in your unit tests within 30 seconds more
  • Hey, nice package! more
  • Behaviors vs Subclassing in Silverlight more
  • Trials & Tribulations of running windows scripts in Vista more
  • Hey, nice package! more
  • Silverlight minor update released today 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