Don,

I would think that it'd be as easy as setting up a separate website in IIS with your apps' virtual directory to avoid conflicts with the dnn website. FWIW I'm not all that impressed by the dnn stuff, at least in the context of the website that a long gone developer here decided to use it on... the whole framework seems to continue a long standing tradition I've run into with web developers that consider ctrl-c+ctrl-v to be re-use rather than actually using ctrl-x+ctrl-v to move reuseable code into a class library.

>I'm probably not smart enough to answer your question. My situation is this. We have an enterprise server that runs our organization's main website. It is loaded with dotnetnuke and the main website which was written by a consultant uses it (dotnetnuke). I have an ancilliary web application that does not use dotnetnuke. When we loaded it onto the server it produced errors to the effect that it was trying to inherit the webconfig settings that are established by the dotnetnuke framework for the main website. Our administrator was able to find a way to prevent the inheritance but I don't know precisly what he did. If you want I can put you in touch with him. Send me a private message with your email address.