I am trying to automate the installation of a DotNetNuke website. We keep the xcopyable DotNetNuke files in Team Foundation Server, and during our continuous integration process we want to:

• Delete all files from the old installation
• Deploy the DotNetNuke runtime files
• Deploy all of our modules into the \Install process for the scheduler to pick up
• Have the installation run and upgrade the database if necessary (newer versions of DNN)

We would like to avoid anyone needing to run the install.aspx page manually - it should be done as part of our build. At the end of the automated continuous integration/deployment process, we should be able to send an email to testers with a hyperlink to the site - no manual steps necessary.

1) Can we do automatic install/upgrade of our database and all the necessary settings through something other than install.aspx?

2) Is it safe to wipe the folder DNN is installed to before installing a newer versions of DNN or modules?

DNN uses an ASP.NET framework with a code-behind model (http://en.wikipedia.org/wiki/Aspx).  If you look closely at the install directory of any installation package you'll notice an Install.aspx.vb file, it generates dynamic aspects of the install page used during the installation and provisions the site.  The funny thing is I can't find any tags written to Install.htm (even though when I view the source of an installation page after an install there they are) in the /install directory.   I'm currently looking for a way to break this apart to support what has been discussed in these posts.  It's not very pretty to break apart and I'm not sure if it's possible.  Thanks Microsoft. 

Any update on this?