1

I wrote some WebAPI controllers using WebAPI for DotNetNuke 7.0 using this method

Everything worked great.

Today I upgraded DNN to 7.2.1 and upgraded my projects to ASP.NET Web API2 and my services on my local machine are now not working - they return "HTTP Error 404.0 - Not Found".

I think it is something to do with IIS and extensionless URLs - I checked IIS and DesktopModules is not an application as suggested here.

I tried Fiddler and F12 Debugging tools and the message is giving no clues away. How can I debug this to work out where the problem lies?

Community
  • 1
  • 1
Rodney
  • 5,417
  • 7
  • 54
  • 98

1 Answers1

1
  1. The folder that the webapi module is coming from supposed to be not an application, meaning it suppose to use the main web.config.
  2. Check the web.config (file diff), what's got changed between the upgrades.
tatigo
  • 2,174
  • 1
  • 26
  • 32
  • Thanks - Point 2 was the issue - I was missing a whole lot of Assembly BindingRedirects: .... – Rodney Feb 10 '14 at 21:27
  • This doesn't work for me. GET requests work fine, but I am still getting a 404 on POST. :( – Will Strohl Apr 03 '15 at 22:23
  • What version of DNN are you using Will? I am using the latest released DNN and I manually upgraded Newtonsoft (so after every DNN upgrade I have to overwrite about 6 dlls) - it is painful but my services work... messenging on DNN does not though (looks like it might work in DNN 8) – Rodney Apr 05 '15 at 07:37