Hi all

Has anyone had any luck installing DNN under another ASP.NET app? I have an ASP.NET application installed in my root. Let's say it's at www.example.com. I want to install DNN at www.example.com/dnn.  I have made /dnn a virtual directory and defined it as an "Application" in IIS. From what I've read, that makes it a "starting point" so DNN should be unaffected by anything above it. That does not seem to be true. I cannot get the installer wizard to start. It comes up with SQL errors because it tries to connect to the database without connection strings being set. If I try to install the old way by editing web.config then I think it created the first couple of tables and crashed.

If I temporarily rename web.config in the top application then DNN works just fine so it is definitety being affected by it. Setting it as an application is doing something because if I don't do that then I get other errors. I don't quite remember what they were now but they made sense because they were related to trying to set some things at the wrong level in the hierarchy.

It seems that defining an IIS "Application" doesn't give the isolation that Microsoft documentation suggests it does. Any ideas or suggestions would be appreciated.

Ross

Theres been a fair ammount of discussion about this on the forums recently here is one of f the postings I could find. look at foos response and look for otherarticles on that would be my suggestion.

John