Deploying DotNetNuke and separate ASP.NET Application together - Possible Issues?

Posted by TheTXI on Stack Overflow See other posts from Stack Overflow or by TheTXI
Published on 2009-02-28T16:12:00Z Indexed on 2010/04/02 21:23 UTC
Read the original article Hit count: 215

Filed under:
|
|
|
|

I am making this in a proactive attempt to head off any potential problems which could arise from this. The situation is that we are developing an ASP.NET application for a client which will handle the online ordering from their customers. This application is going to be using the same database that their current WinForms application uses (no real issue here).

At the same time we are developing a new front-end website for them using DotNetNuke. The DotNetNuke app will simply be linking to the ASP.NET application for the customers to submit their orders (no need for them to communicate back and forth, etc.)

The plan is to host both applications on the same box at the client location. What I am looking for are potential problems or setup tips which would prevent possible conflict between the two apps (web.config conflicts, etc.) Is there a problem with having both hosted on the same location, how should IIS be set up, etc.?

If there are any external resources also available which could address this, please feel free to link them as well.

© Stack Overflow or respective owner

Related posts about ASP.NET

Related posts about dotnetnuke