Core members feel the pain of upgrades too

Being on the Core is not all fun and games and access to the DNN 5 early Beta's (grin). We run DotNetNuke sites just like everyone else and when a security release comes out we have to upgrade our sites just like everyone else.

Nice to know that when using DNN 4.6.2+ you can just drop the upgrade package on top of the site (after backing up your database and entire directory!) and it just upgrades.

This is great because I have about 20 sites to upgrade and I'm only halfway done... But hey, I'm halfway done! I got home after work and since I told my wife "I will be upgrading DotNetNuke sites all night" she isn't staring at me right now wondering why I haven't come down to dinner.

However I'm getting hungry so it's nice to know I'm halfway done...

FYI - I tried to just drop in the upgrade package on a DNN site before 4.6.2+ and I got a yellow screen of death "Could not find file 'c:\SiteUrls.config'." If performing an upgrade with a version prior to DNN 4.6.2 you have to transfer the settings from web.config to the new release.config and then rename release.config to web.config. The settings you need to transfer are the database connection strings and the machine key. Also any entries in the "codeSubDirectories" section.