Today I decided to release a toolkit that I have been building over the past couple of months. Most of the code in the toolkit is related to MVC. Here is a list of the features:
POSTto be made against the action.
Sets the action’s response as cacheable.
Compresses the action’s response using GZip or Deflate encoding.
Marks an action as able to provide the ViewData as JSON, XML, or JSONP.
Marks an action as only able to provide the ViewData as JSON, XML, or JSONP, that means no HTML.
Handles any exceptions thrown from an action, and redirects it to another page, or another action.
I did a whole post on providing a CAPTCHA for your MVC action.
Only the HTTP methods entered in to this filter are allowed for your action. Available HTTP methods are
This view engine provides the serialization of the ViewData to JSON, XML, or JSONP. It is set when one of the following is requested from the ServiceAttribute above.
I did a whole post on why I needed this in my toolkit. Mostly because of my obsessions to have all URL’s in lowercase.
- Redirect extends HttpResponse
I have had a long standing discontent with the Redirect method of the ASP.NET. I have talked about good use of HTTP Status Codes before. There are at least 3 status codes that you want to consider before choosing a response status code of 302. Just to reiterate my post on the subject use 303 to redirect from a form POST, use 307 when you want to redirect to a page that is going to change with each request, use 301 if you want to permanently redirect one URL to another.I created the, Redirect, extension method on HttpResponse so that the status code could be set for the redirect.
Update: I have updated one bug found. Both links above contain the updated source and binaries..NET, IdeaPipe, MVC, Web