Suppose you need to make some DNN core changes to a DNN instance that is already in production. Because the changes will be affecting the server-side code, you must migrate the DNN production instance back to your development environment where you will be able to re-compile the project after you have implemented the code changes.
I know there are tools out there that are supposed to handle this common task, however I have yet to come across one that is dependable. The only sure-fire, fool-proof way that I know to get a DNN site back and forth across development and production machines is as follows...
- Copy Files Copy the project's physical file system (all relevant files) from the source-machine to the destination-machine. *
- Backup Database Create a database backup file (.bak) on the source-machine.
- Restore Database Restore the destination-machine database using the source-machine's .bak file.
- Set File Permissions Make sure that the destination-machine's project folders and files have the correct security permissions set according to DNN installation guidelines (using ASP.NET security group for development, and Network Service sercurity group for production).
(* if going from production to development, the "source-machine" is the one in production and the "destination-machine" is the one in development, or vice-versa if going from development to production)