We have a .net 4.5 mvc solution that resides within a subdirectory on a client's server, view-able in the dynamic web file structure interface as this:
|
|- BellaCenterPdfGenerator
|- Images
|- System
|- Templates
|- ...
|- cache
|- Transhbin
The OurSolutionFolder folder has the standalone project, and requires it's own routing as per mvc to be able to take a url request and direct it to the appropriate controller and run the correct method such as displaying a view.
The solution works great on it's own on our development server, and dynamicweb runs fine on it's own on the clients server. However, putting the .net solution in the dynamicweb environment causes problems. It will give a 404 when we browse to the url:
http://bccph.net.dynamicweb-cms.com/Files/BellaCenterPdfGenerator/Magazine/index
We know that the .net solution can run, because if the Web.config of the standalone solution contains incorrect syntax, we can see a "Server Error in '/' Application." message when we browse to the url. However, if the web.config is okay, we see a 404.
We suspect that the routing that dynamicweb uses interferes with the .net solutions ability to route.
There is a forum post mentioned previously regarding running mvc along side dynamicweb, however the goal in the video and project is creating a custom mvc module for dynamicweb, rather than taking an existing standalone .net solution and being able to run it within dynamicweb's environment.
http://developer.dynamicweb.
Is there a way we can run our solution without the requirement of it being a dynamicweb module?