I am trying to move a DNN site from a Windows Server 2008 server to Windows Server 2012. The problem is that the web.config from the source (WS 2008) isn't compatible with the target (IIS 8.0). I'm assuming this is an IIS 7.0 -> 8.0 issue.  I can't even load the web.config file in IIS Manager.

Anyway, do I REALLY have to start hand-crafting web.config filesDNN drives me crazy with all the manual edits and low-level details necessary for simple, common tasks (move a site from one server to another). Are we still at the point where I have to edit web.config or is there any easier way?

Thanks.

Mark

Thanks for the response. I am very familiar with the need to edit the connection string as I move between machines but that is a simple data issue (wrong machine name, etc). The problem I am seeing seems more about the web.config structure/schema. To reiterate, the web.config file I am restoring comes from a Windows Server 2008 machine and is going on to a Window Server 2012 machine. If this was merely a connection string issue (wrong machine name, for example) I assume I'd be able to at least load the file in IIS Manager. However, IIS Manager complains that it can't load it, which I assume wouldn't happen if I simply has a connection string wrong?

Or am I missing something?

Thanks again.

Mark