Well, release.config must be pretty important, since you have to add your own connection strings, and then rename the thing "web.config" -- but no one has addressed how the connection strings are entirely different from 5.1.2 to 5.4.2.
I have no clue on earth what to do with this thing.
Can't someone come up with a REAL "upgrade" package -- i.e., it takes cares of all this detailed $&%#@ for you??? You know, just takes the connection YOU'RE ALREADY USING and puts up the new software around it???
Yes, I am so angry and frustrated at the lack of a real upgrade utility I am becoming absolutely profane. (it's not an upgrade utility when the "upgrade available" link just dumps you on the download page, in effect saying "you figure it out!")
GRRRRRRRR!!!!!!!! Hair pulling! Head bashing! Giving up!!! I'll try out upgrading to 5.1.4, see if that works any better, because jumping from 5.1.2 to 5.4.2 is NOT!!!!!!!!!!! working. My host is no help either; I asked them if they could update the install they have for DNN, to something more recent; their response was that they don't control the Plesk interface, I should contact Plesk about it. Well, Plesk only wants to hear from you if you're a paying customer -- you know, a webhost. Seems to me that if the webhost doesn't control their own Plesk interface, then no one does. GRRRRRRRRRRR!!!!!!!
I'm thinking this MS server experiment may not last long, and I'm sure glad I only committed to 6 months of hosting for it. I believe I'll be heading back to the sanity of Linux, and Joomla!
Andria