asp.net-mvc-filters

I came across a sample MVC3 code which had following in the Global.asax file: public static void RegisterGlobalFilters(....) { filters.Add(new MyFilter1()); .... var provider = new MyFilterProvider(); provider.Add(c => c.HttpContext.IsDebuggingEnabled ? new MyProvider2() : null); FilterProviders.Providers.Add(provider) } Both MyProvider1 and MyProvider2 are implemented with IResultFilter , and I am confused why one of them is added to FilterProviders and the other one is registered as a global filter. Why and when should we add custom filters on FilterProvider , and why and when should we

I have a filter like this one: public class CustomFilterAttribute : ActionFilterAttribute, IAuthorizationFilter { public MyPropery Property { get; set; } .... } I need it to be run for every actions in my project I tried to register it in the GlobalFilters but my property doesn't get injected I tried This solution to register my filter but it doesn't get called Any idea on how to do that? Pete There's a new way of registering MVC global filters in AutoFac. First, remove the filter registration from your RegisterGlobalFilters because we will have Autofac handle adding them to our controllers

I have a situation where I need to inject some dependencies in a action filter, namely, my custom authorization provider in my custom authorization attribute. I stumbled upon a lot of people and posts who were saying that we should be separating the 'attribute metadata' from the 'behavior'. This makes sense and there is also the fact that filter attributes are not instantiated through the 'DependencyResolver' so it is difficult to inject the dependencies. So I did a little refactoring of my code and I wanted to know if I had it right (I'm using Castle Windsor as the DI framework). First off I