Note that there are some explanatory texts on larger screens.

plurals
  1. POmixed MVC routing for MVC app under web forms app
    primarykey
    data
    text
    <p>I have an instance of BlogEngine.net installed at the root of my hosted server. I wanted to play with ASP.Net MVC to write a small app and installed that app under a folder off the root.</p> <p>I am able to see the <a href="http://example.com/testApp/" rel="nofollow noreferrer">http://example.com/testApp/</a> but the the routed pages like <a href="http://example.com/testApp/edit" rel="nofollow noreferrer">http://example.com/testApp/edit</a> are giving 404's. </p> <p>I have searched around and I'm just not clear what is needed to get the routing right. Do I need to set something in BlogEngine's web.config or do I need to be doing something in my applications settings?</p> <p>The host is WinHost.com and it is IIS7 </p> <p><strong>Edit/Update</strong></p> <p>So I understand that the <a href="http://example.com/testApp" rel="nofollow noreferrer">http://example.com/testApp</a> gets served because there is a default.aspx under that directory and that the routed pages don't get served because they don't have physical aspx's. The /edit gets routed to the edit view just fine when I launch it under Visual Studio. </p> <p>I am guessing that the BlogEngine.net's global.asax is trying to map these pages to the BlogEngine world and not routing them to my testApp.</p> <p>If that is the case then my question is how do I get BlogEngine to forward the requests to my testApp? I was hoping that I was missing something simple in the web.config because if I have to add stuff to BlogEngine's global.asax to do routing then won't I need to rebuild BlogEngine? </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload