HTTP Modules versus ASP.NET MVC Action Filters

Posted by: K. Scott Allen, on 17 Jan 2011 | View original | Bookmarked: 0 time(s)

ASP.NET MVC has action filters, while ASP.NET has HTTP modules. Inside their respective processing pipelines, these abstractions serve similar purposes, and I've heard the following question a few times: When should I write an HTTP module and when should I write an action filter? If you are creating an MVC application then I'll almost always recommend going with an action filter instead of an HTTP module. This is my recommendation even if the functionality you are creating is generic enough to...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: ASP.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 788 | Hits: 78

Similar Posts

  • 12 ASP.NET MVC Best Practices more
  • TIP: How To Generate a Fully Qualified URL in ASP.NET (E.g., http://www.yourserver.com/folder/file.aspx) more
  • How to use Ninject 2 with ASP.NET MVC more
  • RELEASED ASP.NET MVC 2 Preview 2 more
  • WcfTestClient with Windows Azure more
  • Generate stunning ASP.NET/AJAX applications with Web Site Factory more
  • ASP.NET disk-based caching more
  • Quick Reference Guide for Telerik Support more
  • MvcContrib version control has moved to GitHub more
  • Western European ReMix Tour 2009 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