I have two sites I have hosted. Both sites are hosted at a separate URL's for development. Now I want to combine them..   One is a DNN (DotNetNuke) site, the other a custom .Net website app.

So lets say    DNN.domain.com   and CustomSite.domain.com

Both sites run just fine with no problems out of their own urls... however when I virtually include in IIS site2 into site1 like this    DNN.domain.com/CustomSite

I'm getting a .Net Error when I try to browse to that URL. The error that's generated seams to be coming from the webconfig from the dnn.domain.com site, however it's referencing the path of /storefront.. so I'm confused, I thought as long as I virtually included the site, make sure it had it's own app pool (e.g. Make sure it is it's own application in IIS)  the dnn.domain.com site shouldn't run.  Am I running into something weird because of DNN??? and it's alias handling?  Anyone else have issues like this??

If you are embedding another application into DotnetNuke you MUST setup the other application as not only a virtual directory but you must set it to be an "application".

Personally, it is a VERY tricky setup to get working at times, and I highly recommend against it unless you really have a strong need for it.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services