Hello,

I'm a "noob" to these forums but have been tinkering with DNN for a while.

I would like to understand a DNN installation from the standpoint of a simple state machine and actions associates with transitions.

ISP's offer automatic installations.  In the case of my ISP, I can see the results in terms of

BEFORE:

1. There exists an empty target directory which IIS has been configured to treat as the root of a .NET application.

2. There exists an instance of an MSSQL with no tables.

AFTER:

1. The once empty directory now contains a finite number files.

2. There exists a finite number of new database objects.

I have tried to read the installation manuals a number of times.  And I'm sure this is my own failing, but I start to get confused around the part where it handles the cases of both current and legacy versions.

May I inquire from someone who might know this off the top of their head (as I do not expect someone to spend great deals of time to supply mw with information which I could most likely figure out myself through inspection)........

Is it reasonable to construct a "Process View" of the DNN installation as opposed to a "End User Step by Step View" ?

I would be more than happy to put in my own time if this is deemed by others a valuable artifact to add to DNN.

Listen, I know there are gazillions of experts and I know there are people that see "noobs" all the time and want to have the knee jerk reaction of telling me to go read all the docs and "pay my dues".  I would just appeal that I have the technical knowledge of the underlying mechanisms which facilitate DNN as a working portal.  I can leverage this knowledge more efficiently with a little help from "some friends" if you will.

Regards,

Aaron Anodide