Based on the site you pointed me to, Ive been concentrating only on the steps for a development machine virgin upgrade, ie those necessary to upgrade the 4.4 install your setup program creates (without any additional modules, skins, config changes, or user data are added) to a 4.5.5 install. It looks rather simple (maybe too simple?). Basically it is saying to stop IIS, back up the web config, copy all the new install files over the old ones, and then copy back changes in the web-config before re-starting IIS and going to the site to force a compile.
However, Im not sure if all the items he says should be copied from the old web config are necessary in the virgin case.
Clearly, the database connection strings need to be copied. As does the db owner information.
In particular, he says that you should copy the encryption keys. But if you skip that, wont it just create new ones?? Im asking, I dont know.
Also, he says to copy the code subdirectories. What are the code subdirectories exactly? Are those needed?
Im thinking that the entire process to turn the 4.4.1 setup program into a 4.5.5 setup program is basically:
1. Stop IIS
2. Backup the 4.4.1 web.config file as old.config
3. Copy the 4.5.5 install files over existing 4.4.1 files
4. Rename release.config -> web.config
5. Copy both db connection strings from old.config to web.config
6. Copy the db owner fields from old.config to web.config
7. re-start IIs
8. Go to the directory in the web browser
What do you think? If it sounds reasonable to you, Ill try it when I get home and if it works, then for some people it could really be a quick solution.... until the next version of the install is released. And it will always be an option for whenever the installer doesnt match the current version.
Or am I over-simplifying things?