Support Staff4 Posted by friism on 31 May, 2011 09:19 AM
We generally log exceptions and make them available in under
"Errors" in the application interface. 404-errors are not logged
I'm attaching a screenshot of the error. There seems to be a
problem with the route registration, since the handler is
StaticFile. I've tried replacing your App_Start code
with a more traditional Global.asax, to no avail.
It might make sense to post this question on StackOverflow,
since hosting WCF Web Api services is of general interest, and just
to get some more eyes on it.
I really think that might be the issue. I updated my local IIS
and set the ExtensionlessUrlHandler-Integrated-4.0 to handle *.adad
and since that doesn't map to the route I try to access the static
file handler was used instead and I got the same error as you.
You are true, it is really strange. The app itself should be
self contained as long as the
ExtensionlessUrlHandler-Integrated-4.0 handle is configured. No
answers on SO yet. Is it possible to see what has actually been
deployed? Or maybe get a copy of that and try to deploy the code
locally? Have you tried to deploy a wcf web api app your self?
We may be able to resolve this on our end too (seems there's a
hotfix for it) http://support.microsoft.com/kb/980368
. We'll look into that and get back to you if it's no longer
necessary to specify the runAllManagedModulesForAllRequests