We've seen not one, but two posts this week where we used an ActionFilter as the solution to a problem. ActionFilters are powerful. ActionFilters can inspect and modify action parameters and action results. They can cover almost any cross-cutting concern in ASP.NET MVC: caching, security, auditing, etc. But, should you use them everywhere? [Log, UnitOfWork, PreParseParams]
[CommonData, VerifyRedirects, HandleError]
public class BusyController : Controller
{
}
Think about the other options:
HttpModules see the big picture. They can hook into the beginning of a request before a request even knows it's destined for a controller. Modules are...