Comments on: ASP.NET MVC re-factoring

By: Scott

Scott — Thu, 31 Jul 2008 21:18:31 +0000

It still seems like there are two separate operations going on here, one with a POST context, and one with a GET context. Maybe two separate controller methods are needed?

But I see what they are doing there with the attribute.

By: ASP.NET MVC Archived Blog Posts, Page 1

ASP.NET MVC Archived Blog Posts, Page 1 — Thu, 31 Jul 2008 04:41:46 +0000

[...] to VoteASP.NET MVC re-factoring (7/30/2008)Wednesday, July 30, 2008 from http://www.lazycoder.comI agree with his point and one of the MVC developers [...]

By: Ben Scheirman

Ben Scheirman — Wed, 30 Jul 2008 22:51:53 +0000

Actually Scott, the reason they have that in there is so that the can dual purpose the action.

MVCContrib has an attribute called [PostOnly] which you’d use on things like:

//usercontroller
[PostOnly]
public ActionResult Delete(int id)
{
….
}

to prevent someone from navigating to that url.

This attribute is now replaced by the frameworks [RequireHttpMethod("POST")] attribute.

The example you show allows them to have a single action, and if you POST to it you get different results. I don’t think I like it very much, but it’s a pattern I’ve seen a few places.

By: Alan Stevens

Alan Stevens — Wed, 30 Jul 2008 22:23:17 +0000

Scott,

In preview 4 there is a RequireHttpMethodAttribute in Microsoft.Web.Mvc.dll that removes the need for this code.

++Alan