>>>My only guess is that he just wanted to re-invent something that is already built in to the framework using his own code<<<

Who hasn’t reinvented something in a/the framework with their own code at some point?

Pretty thin-skinned considering the troll jobs I’ve seen you do on other people. I hope some Hawaiian beats you senseless with your sunscreen bottle while you’re floundering in the shorebreak trying to get another action pic for your blog.

http://code.google.com/p/coderjournal/source/browse/trunk/ManagedFusion.Web.Mvc/MvcExtensions.cs
http://code.google.com/p/coderjournal/source/browse/trunk/ManagedFusion.Web.Mvc/WebExtensions.cs

Thanks.

Like redirects - even custom ones. You can also test to see if a user is logged in before tossing an Exception. If you noticed in my sample where I check a Role, I first see if the user’s logged in - if they aren’t redirect them while appending the proper Return. Your example above throws an Exception - which you’d have to code your way out of to handle properly.

Finally - I’m not sure why you’d suggest the code is “Nasty” because it references FormsAuthentication. This is by way of example of course, so if you wanted to use a different Auth Scheme you could.

>>>My only guess is that he just wanted to re-invent something that is already built in to the framework using his own code<<<

That was unnecessary. I know you probably didn’t mean to insult, but that’s what it is.

Source for ExceptionHandlerAttribute:
http://code.google.com/p/coderjournal/source/browse/trunk/ManagedFusion.Web.Mvc/ExceptionHandlerAttribute.cs

Also Rob’s solution had the nasty habit of assuming everybody was using Form Authentication, if I tried Passport, Windows, or Basic authentication I would be out of luck. That is why as demonstrated in the example below that set the status code to “401 Unauthorized” and then let whatever authentication module that I am using pick up on the status code and redirect me to a login page for Forms Authentication or pop open a Windows dialog for my credentials or take me off to a Microsoft Password authentication page.

So I would do the following to my method to let the 401 float down to the EndResponse and then let the FormsAuthenticationModule or WindowsAuthenticationModule pick up the HTTP 401 Status Code and do what ever it does depending on what type of authentication you are using.

[PrincipalPermission(SecurityAction.Demand, Name = "SiteAdmin")]
[ExceptionHandler(401, "Unauthorized", typeof(SecurityException)]
public void RolesAdmin () {
RenderView(”RolesAdmin”);
}

Or I can redirect them to the correct action depending on the exception that is thrown

[PrincipalPermission(SecurityAction.Demand, Name = "SiteAdmin")]
[ExceptionHandler("Login", "User", typeof(SecurityException)]
public void RolesAdmin () {
RenderView(”RolesAdmin”);
}

Thanks,
Nick