Hi guys! I have a custom MVC Module with the following routes configured:
- mapRouteManager.MapRoute(<moduleName>, "default", "{controller}/{action}", new[] { <moduleNamespace> });
- mapRouteManager.MapRoute(<moduleName>, "default", "{controller}/{action}/{resource}", new[] { <moduleNamespace>});
I have a HTTP/Text Module that interacts with theWeAPI and everything works fine and the world is great. I can even call any method using fiddler (e.g., http://hostname/DesktopModules/MVC/<moduleName>/<Controller>/<Action>).
Now the trouble begins. I installed a third party module that also registers two routes:
- mapRouteManager.MapHttpRoute("MyDnnSupport.LiveChat", "default", "{controller}/{action}", new[] { "MyDnn.Modules.Support.LiveChat.Services" });
- mapRouteManager.MapHttpRoute("MyDnnVisitorsOnline", "default", "{controller}/{action}", new[] { "MyDnn.VisitorsOnline.Services" });
After installing this extension, my module breaks. Any request, to my module (webpage or fiddler), returns 404 Not Found. If I restore my DNN and Database to the point before installing the extension, everything works again.
I already checked if IIS had turned my module into a Virtual Application, but that's not the case.
I also tried to change the "default" part of the route to something else, but nothing changes.
Is this problem a conflict between the route mapping of both modules? What can I do to fix this?
Thanks,
Artur Albquerque