> > > http://blogs.msdn.com/b/webdev/archive/2013/04/04/debugging-asp-net-web-api-with-route-debugger.aspx >
I tried following this and adding a Nuget package, but it bloated the tiny project to a huge size and it wouldn't show the cshtml page when I set it as the start page. It made such a mess I deleted my whole project and folder and made a fresh one. Pardon me, but I thought Web API development would be trivially easy, but I keep stumbling upon gotchas and basic functionality "hidden" so it can only be found in extensive Google searches. As soon as I want to do anything that isn't in the kindergarten tutorials I'm up sh*t creek and spend most of the day web searching as usual. No one so far has discussed the app lifecycle and where things should live for how long, nor has anyone explained how to scale-up with lots of controllers and rules. I'm extremely disappointed with what I've found in my first exploration this morning. The Web API seems to be another one of these bloated infrastructures (like ASP.NET) which takes a simple idea and turns it into a Rube Goldberg machine <http://en.wikipedia.org/wiki/Rube_Goldberg_machine> . Greg
