In my controller I have two actions called "Friends". The one that executes depends on whether or not it's a "get" versus a "post".
So my code snippets look something like this:
// Get:
[AcceptVerbs(HttpVerbs.Get)]
public ActionResult Friends()
{
// do some stuff
return View();
}
// Post:
[AcceptVerbs(HttpVerbs.Post)]
public ActionResult Friends()
{
// do some stuff
return View();
}
However, this does not compile since I have two methods with the same signature (Friends). How do I go about creating this? Do I need to create just one action but differentiate between a "get" and "post" inside of it? If so, how do I do that?
not entirely sure if it is the correct way, but i would use a meaningless parameter to differentiate the sigs. like:
I know it's ugly and hackish, but it works.
Rename the second method to something else like "Friends_Post" and then you can add
[ActionName("Friends")]
attribute to the second one. So the requests to the Friend action with POST as request type, will be handled by that action.add to the Post method the params to want to receive in the post. maybe like this:
..or if you have a complex type, like this:
Edit: It would be preferable to use a more typed-approach to receiving the posted items, like above.
Your action methods can't be doing the same thing, otherwise there would be no need to to write two action methods. So if the semantics are different, why not use different names for the action methods as well?
For example, if you had a "delete" action method and GET just asks for confirmation, you might call the GET method "ConfirmDelete" and the POST method just "Delete".
Not sure if that matches your scenario, but it always did for me when I had the same problem.
Marking cagdas' response as the answer since it answered my question. However, since I don't like using the ActionName attribute in my project I use a different solution. I simply added the FormCollection to the "post" action (which ends up changing the method signature)
If you truly only want one routine to handle both verbs, try this:
One potential caveat: I'm using MVC release 2. Not sure if this was supported in MVC 1. The Intellisense documentation for AcceptVerbs should let you know.