Moving a site from development to a Production instance, using site wizard to replace the default DNN portal.  Both have same DNN 6.2.5, the dev is asp.net 3.5 and the prod version is asp.net 4.0.  Everything seems the same except this, can it cause it not to work?  All modules, skins, containers, are loaded and ready. 

Thanks

Doug,

you should first move your installation to an asp.net 3.5 site and then increase the asp.net version - or (even better), first increase the asp.net version on your development environmet, test it and then move it.

Anyway, I never used a wizard for this. It is fairly easy to do it manually. So here are short instructions how to do it if you want to try:

1. Make a backup of your database, and a backup of your DNN installation (I use 7zip for the latter).
2. On your web server, create a folder (eg. D:\DNN).
3. Use IIS Manager to create a website that points to this folder. Remember the Application Pool that this site is running under (either create a new one, eg. DNNAppPool, or use an existing one with the correct ASP.Net version).
4. Restore the database on your production environment.
5. Restore your DNN installation to the folder that you created in step 2.
6. Change the two connection strings in your web.config to point to the correct database.
7. Correct the portal alias in the table PortalAlias.
8. Check permissions (both on the database and the file system) and you should be done. The user who needs db_owner role membership on the database and modify permissions on the DNN installation is depending on your environment (SQL/IIS on the same or different machines) and the Windows/IIS version you use. Don't hesitate if you need details, but please post details of your setup if I shall give you more information.

Best wishes
Michael


Best wishes
Michael

---