Home/ Questions/Q 7536491
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T06:35:17+00:00

The standard route for the MVC Web API is {controller}/{id}. However I’d like to

  • 0

The standard route for the MVC Web API is {controller}/{id}. However I’d like to name my variables more descriptively then just ‘id’. To do this though it would make more sense to me if I could map routes directly to methods as the WCF Web API worked. Is there a way to do this with MVC or is there is a more MVCish way of routing but still maintaining unique identifiable placeholders for each method?. Or am I stuck just naming all my parameters id?

    [WebGet(UriTempalte="{controller}/{email}"]
    public string GetEmail(string email)

Instead of:

    public string GetEmail(string id)
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you name it email – then create a separate Route in Global.asax.cs naming your parameter accordingly, i.e. {controller}\{email}. In MVC routes you only have a very short list of MVC-specific keywords – {controller}, {action}, {area} etc. All the other parameters are passed to corresponding action parameters (if they are present in your action method signature of course).

    • 0