What is the deployment strategy for moving modules and pages between development and production? Or to another development computer. From what I see so far the process is not good. I have to run the sql scripts to add the module to production, then I have to re-create the pages in production and put the module(s) on the page. Is this the correct deployment strategy, cause if so it sucks.

Is there not a way to script this out? Especially the page creation?

On another note, why can I note copy the sql database and the entire web project folder to another computer, create a virtual directory to the web folder, ensure proper permissions to DNN database and have be able to develop or run the web app on this 2nd computer? I have tried this before and get weird errors like it wants to do a DNN upgrade, which typically errors out and I get the screen that says, "The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] ) " what does that mean? I copied the database from a machine that worked. I typically have to delete the DNN database with all the modules and pages already loaded, and have to let the database get created all over again, and then have to re-load the sql for the modules and re-create the pages all OVER AGAIN.

Help please, I'm tried of being pissed off about how sucky this is. Then I can praise it.

Thanks ....

I'm looking for solutions for the same problem, have you had any breakthroughs yet?

Is there a way to script the DNN database changes, even small changes like content changes, new page creations and settings changes on a development box and then use the SQL script to deploy to the production server?

Let me know if this is possible or if a work around is possible.