o_19mgorv9t13a3ko71fev19l81mqa.pdf

public string RangeTest(int id) {
if (id > 100) {
return String.Format("The id value is: {0}", id);
} else {
throw new ArgumentOutOfRangeException("id", id, "");
}
}
public string FilterTest() {
return "This is the FilterTest action";
}
protected override void OnActionExecuting(ActionExecutingContext
filterContext) {
timer = Stopwatch.StartNew();
}
protected override void OnResultExecuted(ResultExecutedContext
filterContext) {
timer.Stop();
filterContext.HttpContext.Response.Write(
string.Format("Total elapsed time: {0}",
timer.Elapsed.TotalSeconds));
}
}
}
I removed the filters from the FilterTest action method because they are no longer required. The Home controller will
add the profile information to the response for any action method. Figure 18-11 shows the effect of starting the application and
navigating to the /Home/RangeTest/200 URL, which targets the RangeTest action without causing the exception I
set up to demonstrate the HandleError filter.
Figure 18-11. The effect of implementing filter methods directly in the controller
This technique is most useful when you are creating a base class from which multiple controllers in your project are derived.
The whole point of filtering is to put code that is required across the application in one reusable location, so using these methods in
a class that will not be used as a base for controllers does not make much sense.
Tip I prefer to use attributes. I like the separation between the controller logic and the filter logic. If you are looking for a way
to apply a filter to all of your controllers, continue reading to see how to do that with global filters.
Using Global Filters
Global filters are applied to all of the action methods in all of the controllers in your application. There is a convention for setting
up global filters, which is created by Visual Studio automatically when you use the MVC project template but which must be set
493