Different RoutePrefix, same controller name

Question

I'm having a problem with splitting my web-api application into different areas (not mvc areas), using namespaces and RoutePrefix

The application is hosted using Owin Self Host, and in my Startup class I have the following.

HttpConfiguration config = new HttpConfiguration();
config.MapHttpAttributeRoutes();
app.UseWebApi(config);

And my two controllers that I tested with

[RoutePrefix("api/test")]
public class TestController : ApiController
{
    [Route("")]
    public IHttpActionResult Get()
    {
        return Ok("api");
    }
}

[RoutePrefix("sync/test")]
public class TestController : ApiController
{
    [Route("")]
    public IHttpActionResult Get()
    {
        return Ok("sync");
    }
}

These two controllers live in two different namespaces, Api and Sync.

When I try to access the two controllers with http://localhost/api/test and http://localhost/api/sync I get a 404.

But If I rename one of the controllers to e.g. TestApiController then both works.

Someone having a good idea if it's possible to do what I want?

score 20 · Accepted Answer · edited Sep 07 '16 at 20:16

20

Unfortunately, Web API finds controllers by class name, ignoring the namespace. This is a known issue and is not unique to attribute-based routing.

The easiest work-around by far is to avoid the problem and use unique controller names. But if you don't mind getting a little fancy, here's a solution:

https://blogs.msdn.microsoft.com/webdev/2013/03/07/asp-net-web-api-using-namespaces-to-version-web-apis/

edited Sep 07 '16 at 20:16

Jason P

1,415
14
12

answered Apr 14 '15 at 12:54

Todd Menier

37,557
17
150
173

Ok. Thank you. Guessing unique names are the way to go then. – Jens-Christian Skibakk Apr 14 '15 at 13:05
THIS, I struggled to find out why my seemingly correct routes were not working. Thank you – Carlitrosss May 31 '16 at 14:32

Different RoutePrefix, same controller name

1 Answers1

Linked