Just a quick question for you Mitchell.  Does it make any difference if one just modifies the existing web.config?  I did that on a clean install for testing 4.5.1 and it installed beautifully.  Took about 15 minutes, including setting up the new DB, virtual directory in IIS and setting Asp.Net User permissions.

I was very "wary" about 4.5.1 having seen so many negative posts, but so far I am pretty/amazingly happy with what I see, especially all the work Locopon did on FCK.  I tested loooooots of editors, FCK, FTB, Free Text Box, TinyMCE, etc. a while back and FCK was way beyond the rest.  Good work Locopon!!

In any event, unless there is something I am missing, shouldn't modifying the existing web.config in either a fresh install, or an upgrade work just fine?

Clay

I guess it's just "one of those things."  Probably would be better if that part were standardized and either web.config were changed every time and the "release.config" never issued, or the process of releasing only with release.config and web.config was never issued.  This in one of those little areas of DNN that seems to create confusion and problems.

I normally rename release.config as well, and I understand migrating the sections needed, such as the connection strings, the machine keys section, the app subdirectories, etc.  Just thought I would try it this way to see what happened this time.

I did read the article on your site a while back and really enjoyed it.  Especially the part of using app-offline.htm for upgrading. 

Clay