Is there a document that describes the upgrade process for moving from DNN 3.3.5 (or .6 or .7) to DNN 4.3.7? Since DNN 3 is going away, I need to migrate a few of my installs to the DNN 4 versions. Thanks for any help you can provide.

UPDATE: I finally got the right search term to yield a few posts on the general upgrade process. So I have a little info to start with. For some popular third party modules, like Active Forums and XMod, both of which I use heavily, would I need to upgrade to a DNN 4 version just for them to work or would the DNN 3 version work to accomplish the upgrade and then I could upgrade these modules later to a DNN 4 version?

Got it...duh! So it looks pretty straightforward. I will start with one of my DNN installs that only has my websites on it and no customer sites.

I saw many posts talking about deleting .vb files before so there will not be duplicate declarations. I am not a developer and thought that the .vb files in a folder were only there for development. So I deleted the vb files from a folder and the site stopped working. I just did a quick restore from the recycle bin. So I guess that the deletion is not something I can do up front and then work on the upgrade over time...it all has to be done pretty quickly and all at once. Am I correct on this and if you can explain what the vb files do it would be nice.

When I move from WH4L to a dedicated server I went from SQL Server 2000 to SQL Server Express 2005. But I have never changed any of my connection string setup...other than the server name...and it works. So what is the purpose behind the different connection string format suggested for SQL Server Express? Do I really have to have it?

Thanks.