Access Web API routing from ASP.NET MVC application

Question

I have a solution with 2 projects. One is an ASP.NET Web API project and the other is an ASP.NET MVC project. The web api will be consumed from various clients. If the 2 projects were one I could generate a link for my api like this:

@Url.RouteUrl("ActionApi", new { httpRoute = string.Empty, controller = "User", action = "AddChildAsync" });

But now that these 2 projects are separated I cannot do this because the mvc appliction cannot find the configuration for the web api (although I have a project reference from the mvc app to the web api). So is there any elegant way to access web api configuration and generate links dynamically? Thanks in advance.

The WebApi configuration is global to the application, so if you just add the WebApi nuget package into the MVC project, and maybe add the System.Web.Http namespace to your Views/web.config, does that not work? — Rhumborl
– Rhumborl, Commented Dec 6, 2014 at 12:03
@Rhumborl I tried your suggestion but I get the same error ('A route named 'ActionApi' could not be found in the route collection.'). Thanks for your answer. — Giorgos Manoltzas
– Giorgos Manoltzas, Commented Dec 6, 2014 at 12:13

Ashley Lee · Accepted Answer · 2014-12-06 13:03:43Z

2

You should be able to access it by changing httproute = true.

@Url.RouteUrl("ActionApi", new { httpRoute = true, controller = "User", action = "AddChildAsync" });

Or you could do this to specify it a webapi route.

@Url.HttpRouteUrl("ActionApi", new { controller = "User", action = "AddChildAsync" });

But you do need the WebApi registration done in your Global.asax and have the NuGet WebApi package installed.

Also, typically actions aren't included in the route as you've referenced above in your links. They're typically unnamed and provided by request (GET, POST PUT, ect). Those are omitted unless your route config looks something like this.

routes.MapHttpRoute(
name: "ActionApi",
routeTemplate: "api/{controller}/{action}/{id}",
defaults: new { id = RouteParameter.Optional } );

edited Dec 6, 2014 at 13:03

answered Dec 6, 2014 at 12:57

Ashley Lee

4,0162 gold badges21 silver badges27 bronze badges

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

1 Comment

Giorgos Manoltzas Over a year ago

Thank you for your answer. Your solution works like a charm. I have modified the default routing that is why I include the actions in the route as you mentioned.

Alex Art. · Accepted Answer · 2014-12-06 12:33:44Z

I had a similar issue once.

My solution was creating interfaces for each one of the WebApi controllers that could be shared among your projects (MVC and WebApi). To each one of the WebApi controllers add an action (I will refer to it as 'Routes' action) that returns serialized Collection of key-value elements, where keys are interface (WebApi) method names and values are objects that contain routes and http methods (Get,Post etc) (It is constructed in WebApi project so you have access to it's routing table).On MVC application start you can issue a request to your WebApi Routes action and get all it's routes. Then you can store it in a global readonly dictionary for a quick access. Getting a particular route becomes a trivial task because your interface method names are keys to the dictionary you filled earlier.

Collectives™ on Stack Overflow

Access Web API routing from ASP.NET MVC application

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related