Route Prefix VS Controller Name ( Web api )

Question

I was wondering that if we use RoutePrefix attribute in our web api controller with a different name from controller's actual name. So would it work or not?

As far as i did

[RouterPrefix("quotation")]
public class SaleOrderController : ApiController { ... }

if we define RoutePrefix like above we can't access it via /quotation but we can access it using saleorder.

So what is RoutePrefix for or am i doing something wrong ?

Answer 1

To use default route use Route("")

[RoutePrefix("quotation")]
public class SaleOrderController : ApiController {

    //GET quotation
    [Route("")]
    [HttpGet]
    public IHttpActionResult GetAll() { ... }

}

Source: Attribute Routing in ASP.NET Web API 2 : Route Prefix

Answer 2

In order for it to work, you need to call the code below inside your WebApiConfig.Register() method:

config.MapHttpAttributeRoutes();

So your RoutePrefix works as exptected:

[RoutePrefix("quotation")]
public class SaleOrderController : ApiController
{
    [Route("example")]
    [HttpGet]
    public IHttpActionResult Example()
    {
        return Ok();
    }

    [Route("another")]
    [HttpGet]
    public IHttpActionResult Another()
    {
        return Ok();
    }

}

So your could access your apis like this:

• quotation/example
• quotation/another