Couple of things to understand and a question or two.

A CMS pretty much takes control of the page display process at the lowest possible level of operation that a web server offers.  To do this it hooks into the asp.net application cycle at its core taping directly into things like httphandlers and the global.asax object level layer.

As such - it is doing this to every http request BEFORE the usual get http page cycle that many people understand even begins.

If you place any .aspx page, anywhere inside, any FOLDER, below the DNN root folder - requesting that page will cause this cycle to commence.
This is called amongst other things the application space of the web application.

However on the OTHER hand if you create an application sub-folder with its OWN web.config in a folder below the DNN root you start to get into a messy area - what is happening now is asp.net at work - when you create an application sub-folder - you are telling asp.net that you want to create a separate application space in the sub-folder - BUT - doing so gets things confused - because the DNN application now no longer controls the folder - BUT due to the way asp.net works the new application still tries to inherit the items defined in the web.config - BUT without the global.asax application ever executing.

So as a result you loose all the functionality of the DNN CMS by creating a sub-folder application.

I guess the question comes down to what you are trying to achieve in your small application - it could most likely be run as a module inside DNN which would give it full access to the DNN application space - but then again there may be little point of doing so.

Westa

Hey Jim,

Sounds like a good approach to things - and you keep the benefits of the DNN environment for editing etc if you so desire.

Cheers

Wes