Reputation: 4302
I upgraded an existing MVC4/WebAPI1 project to MVC5/WebAPI2 in Visual Studio 2012 as described here. The site worked as expected. I then followed the directions for attribute based routing found here - except I keep getting a 404 for the controllers. My steps were:
I see that the test route is getting registered when I put a break after config.EnsureInitialized(). However, trying to hit that route gives me a 404.
If there any way out of the box to inspect the request and see how the routing table is being matched?
Upvotes: 9
Views: 7842
Reputation: 526
I had the almost the same issues. And cannot find any working solution. The Route debugger is really doesn't work with Web API 2. Finally, I've found a working way to debug Web API 2 including Route Attributes.
Microsoft.AspNet.WebApi.HelpPage
Нope this helps someone save a few hours of debuging.
Upvotes: 14
Reputation: 6839
You can use Route Debugger
to inspect all Routes. There's an official post from MSDN that covers this:
Upvotes: 0