CBOSS INC
Nuke Pro
Posts:61
 |
| 02/02/2009 3:23 PM |
|
Unless I'm missing it, I'm not seeing any difference in the videos 2 and 3 that demonstrate the difference between the Auto Merge Method of upgrade and the Manual method of upgrading? Where's the Auto Merge Method?
Also- please delete my post for Issue 40- wrong issue, wrong subject |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 02/02/2009 5:50 PM |
|
Short summary:
The Auto-Merge method doesn't require that you copy items from your old web.config file to a new one. You simply unzip the UPGRADE DotNetNuke package into your web directory.
The Manual method requires that you move some items from the prior web.config to the new one. Since it's manual, it is prone to error. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
CBOSS INC
Nuke Pro
Posts:61
|
| 02/03/2009 10:41 AM |
|
But you still need to copy over information such as connection strings, app settings and machine keys? So it's still a manual process. I thought that it would somehow merge the contents of my current web config with the update web config |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 02/03/2009 11:53 AM |
|
No, the whole point is that you no longer have to copy anything from your old web.config. The "auto merge" part of the upgrade process does that for you. Settings from your old web.config are used in the new one.
|
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Dan Whitacre
Nuke Ace
Posts:45
|
| 02/21/2009 12:57 PM |
|
Joe,
Just to be clear, the auto-merge method is not available for upgrading DNN versions prior to 4.6.1, correct? I am upgrading a 4.4.1 install and I will need to make all those changes for a 4.9.1 upgrade....AM I CORRECT? |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 02/21/2009 12:59 PM |
|
I think you have to have upgraded to 4.6.2 to be able to use auto-merge for upgrades. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Lee Sykes
DNN Creative Staff
Nuke Master VI
Posts:4945
|
|
Dan Whitacre
Nuke Ace
Posts:45
|
| 02/23/2009 7:36 AM |
|
So, is there any reason why I shouldn't just do a manual upgrade to 4.9.1? If not, I think I just need to connect the db in two places (I don't need to mess with the machine key, correct?).
|
|
|
|
|
Lee Sykes
DNN Creative Staff
Nuke Master VI
Posts:4945
|
| 02/23/2009 8:30 AM |
|
You can use the manual method to upgrade to whatever version you require.
However I would test it first before attempting on your live site. You may find you get errors and if you do the solution will more than likely be to upgrade to 4.6.2 first and then to 4.9.1.
If you decide to go straight to 4.9.1, use the manual method as outlined in the tutorial, make sure you copy across the required fields such as connection string, machine keys, installation date, etc.
|
|
Lee Sykes
Site Administrator
Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts
Twitter: www.twitter.com/DNNCreative
 |
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 02/23/2009 8:49 AM |
|
I would say that the manual method is more prone to errrors than the auto-merge method.
Also, upgrade to 4.9.2 rather than 4.9.1. That upgrade was released a week ago and fixes some errors in the 4.9.1 release.
|
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|