ASP.NET WebAPI Attribute Routing on Duplicate Class Names

Question

I ran into this problem when attempting to version one of the APIs that I'm working on.

I have 2 controllers that are named the same, are in different namespaces and are mapped to different routes. When I attempt to go to their different routes I get the error No HTTP resource was found that matches the request URI.

Here's a code example:

namespace MvcApplication
{
    public class WebApiApplication : System.Web.HttpApplication
    {
        protected void Application_Start()
        {
            GlobalConfiguration.Configure(WebApiConfig.Register);
        }
    }
}

namespace MvcApplication
{
    public static class WebApiConfig
    {
        public static void Register(HttpConfiguration config)
        {
            config.MapHttpAttributeRoutes();
            config.EnsureInitialized();
        }
    }
}

namespace MvcApplication.Controllers.v1
{
    [RoutePrefix("api/v1/values")]
    public class ValuesController : ApiController
    {
        [HttpGet]
        [Route("")]
        public IHttpActionResult GetValues()
        {
            return Ok(new string[] { "value1", "value2" });
        }
    }
}

namespace MvcApplication.Controllers.v2
{
    [RoutePrefix("api/v2/values")]
    public class ValuesController : ApiController
    {
        [HttpGet]
        [Route("")]
        public IHttpActionResult GetValues()
        {
            return Ok(new string[] { "value3", "value4" });
        }
    }
}

If I change the class names so that they aren't the same (such as ValuesControllerV1 and ValuesControllerV2) everything works as expected.

Is there anyway to keep the same class names and have things resolve as expected?

EDIT: Updated to show initialization code as well.

Are any of the routes registered in this case? Or do you get No HTTP resource was found that matches the request URI for both? — James
– James, Commented Aug 14, 2014 at 15:30
Yes, attribute routing is enabled. If I simply change the name of the classes everything works. — Bengel
– Bengel, Commented Aug 14, 2014 at 17:07
@James The default routes were in place and were working fine. I've removed them all to fit this example more specifically. Even still simply changing the class names makes the routes work just fine. — Bengel
– Bengel, Commented Aug 14, 2014 at 17:17

Oualid KTATA · Accepted Answer · 2014-08-14 18:37:32Z

0

IN MVC you can use the MapRoute Overload that has a namespace argument. Something like this:

routes.MapRoute(
     "Route for v1", // Route name
     "areav1/{controller}/{action}/{id}", // URL with parameters
     new { controller = "Values", action = "GetValues", id = UrlParameter.Optional },           new string[] { "MvcApplication.Controllers.v1"}
);

routes.MapRoute(
     "Route for v2", // Route name
     "areav2/{controller}/{action}/{id}", // URL with parameters
     new { controller = "Values", action = "GetValues", id = UrlParameter.Optional },           new string[] { "MvcApplication.Controllers.v2"}
);

Unfortunatly, this is not yet implemented in WebApi.

Here is a thread about this problem specifically:

edited Aug 14, 2014 at 18:37

answered Aug 14, 2014 at 18:13

Oualid KTATA

1,11610 silver badges20 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Jasen Over a year ago

Web Api does not use MapRoute so the namepsace parameter is not available.

Collectives™ on Stack Overflow

ASP.NET WebAPI Attribute Routing on Duplicate Class Names

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related