I have a production site that I will transition today to 7.0.5 [on a backup first...] from 6.0.1 [or 2...]

I have upgraded to asp.net 4.5/4.0.  So far my 5.6.x and 6.x sites are still running...  Fingers crossed; you never know...

I will switch from Classic to Integrated Pipeline.  Can I be reasonably certain this will not kill other 5.6.x or 6.x instances running?  I have a number of instances running on the same hosting servers.  This seemed safe until my hoster offered a disclaimer...

Can I install 7.0.5 and fully debug before restoring my copy of production database from backup?  I realize it may not go swimmingly but I want it to be the smart thing to do, not dumb...

Thanks in advance.

Excellent idea.  I only have access to one app pool per hosting account, but I do have several hosting accounts so I could keep one set aside for strictly test.  I can manually move the backup db between accounts...  This has all sorts of merits/advantages.  THANKS!!   Funny, but that was why I started with multiple accounts to begin with...  to test...  Duhhh...

ASP.net and integrated pipeline changes went off w/o a hitch.  Had to change servers, but that brought a much-needed, too-long-avoided performance boost; more than I thought...

DNN 7.0.5 is now installed [new].  I will get all the modules/skins I need installed [some require upgrades themselves], and then try restoring my old 6.0.x database and see if it will run.  Typically machinekey stays with the data; I hope that is still true.   Need to remember to change the machine key this time but leave the connection strings alone...  string around the finger.

Muchas Gracias, amigo...

Bob H.

My backup db is SQL Server 2005  My new db is SQL Server 2008.  When I restore the 2005 backup to my 2008 db the server runs enough to do the conversion, says it is done successfully but then gives me an internal server error 500 when I try to run the web site...  Is there some migration work that needs to be done to make this upgrade work?

Bob