Something I left out of the proposal was one of the advantages of using the Enterprise Blocks to help with DotNetNuke installation.
• The Enterprise blocks store the database configuration in a dataconfig.config file not the web.config file so it can be updated on-the-fly. It can also be encrypted.
• Because the database configuration can be updated on the fly it would now be possible to:
o Distribute DotNetNuke using Microsoft Access
o When a person wants to upgrade to SQL, they:
Log in as HOST and go to settings
Put in their SQL server login info
DotNetNuke checks:
• To see if it can connect.
• It can also see if it’s and upgrade (and if so perform the upgrade)
• If it’s a fresh install it installs the objects and verifies everything is running.
Only then does DotNetNuke change the configuration in the dataconfig.config file and trigger a reload using the new settings.
• If DotNetNuke has a fatal crash it can try to revert back to Microsoft Access. It can either run or simply put up a page that says “This site is down for maintenance” and send an email to it’s owner.
|