Cheers Peter... Thanks for the prompt response... This looks like a good script... Just a few questions embedded in UPPERCASE... just verification mainly :-)
This is what I do:
1. Zip up the whole DNN directory. Name it something silly, put in the web root, and download to your PC
DONE :-)
2. Make backup of SQL database. Zip it, put in web root and download.
DONE... DOWNLOADED AS A .BAK FILE (IS THAT OK?)... IN FACT DOWNLOADED ALL FILES AND THE .BAK FILE USING FTP...ALL SEEMS OK I THINK...
3. Delete zips (from your live webserver).
I PRESUME YOU MEAN CLEAN UP AFTERWARDS SO I DON'T USE UP MORE SPACE THAN REQUIRED ON MY CURRENT HOSTING ACCOUNT? GOOD IDEA...
4. Unpack first zip to your HD. Open properties of root and set NETWORK SERVICE to have full access. Unify on all children.
AM I RIGHT IN THINKING THAT YOU DO THIS IN WINDOWS EXPLORER USING THE 'PROPERTIES' OPTION IN THE RIGHT-CLICK DROP DOWN MENU?
5. In IIS either add this as a new website or a new virtual dir under an existing one. The procedure will be slightly different, but both should work. If adding as a new website make sure to set host header and to announce it in the hosts file. I often use this to copy www.someclient.com to local.someclient.com. Make sure in IIS to set the application and set ASP.NET to be framework 2.0.
GOT IT :-)
6. Open SQL Manager and restore the database. You'll need to edit the location of files most likely.
IS THIS STORED IN A DNN TABLE (WHICH ONE) OR IS THE EDIT FOR THE LOCATION OF FILES SOMEWHERE ELSE?
7. Open DB and add your local account through which you will access the database from DNN.
GOT IT :-)
8. Open PortalAlias and edit the alias for the portal you will be using. Make sure you get this correct.
IS THIS A TABLE CALLED PORTALALIAS IN THE DNN DATABASE?
9. Edit the web.config to correct the SQL connection string.
GOT IT :-)
I think you can now safely surf to the site.
THANKS IN ADVANCE PETER OF ANY DNN FORUM USER... :-)
Peter