Question

What’s the benefit of setting an alias for an action method using the “ActionName” attribute? I really don’t see much benefit of it, in providing the user the option to call an action method with some other name. After specifying the alias, the user is able to call the action method only using the alias. But if that is required then why doesn’t the user change the name of the action method rather then specifying an alias for it?

I would really appreciate if anyone can provide me an example of the use of “ActionName” in a scenario where it can provide great benefit or it is best to use.

Answer 1

It allows you to start your action with a number or include any character that .net does not allow in an identifier. – The most common reason is it allows you have two Actions with the same signature (see the GET/POST Delete actions of any scaffolded controller)

For example: you could allow dashes within your url action name http://example.com/products/create-product vs http://example.com/products/createproduct or http://example.com/products/create_product.

public class ProductsController {

    [ActionName("create-product")]
    public ActionResult CreateProduct() {
        return View();
    }

}