This may seem like a fairly rudimentary question, but how does DotNetNuke dynamically load each page? Where does it construct the pages? Is this included in the source code?

I am trying to use a DNN portal for an intranet site in retail stores on a very scaled down version of IE6 that does not allow MANY things. I know I could be grilled in a detailed manner about DNN prior to production. Any insight for me?

Thanks!

Kellie wrote This may seem like a fairly rudimentary question, but how does DotNetNuke dynamically load each page? Where does it construct the pages? Is this included in the source code?

DNN runs on the ASP.NET framework, and uses ASP.NET technology for accessing databases and files on the system  When a page is requested, it is dynamically created by the ASP.NET framework according to the DNN code, based on entries in a database and files within the file system.  The response from the framework is sent as HTML to the browser, and may include client side code (JavaScript) for functionality within the page.  DNN can also use AJAX.

The "source" for DNN lies on top of the ASP.NET framework, so you need both installed on the server.  As for where the pages are constructed, the answer is in  memory, which is saved in a cache according to DNN and ASP.NET settings for future use if needed.  There is no permanent "page" created, the entire process is dynamic with every request.

To fully understand this, you'll need to understand ASP.NET as well as DNN.

Jeff

TMMworld wrote Hmmm... I always thought that it all just happened automagically.

Ah.....  that bit is generally handled by the DNN Core Team, beats me as well ... :).