Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...311 to 435: Recommended path?311 to 435: Recommended path?
Previous
 
Next
New Post
10/22/2006 3:05 PM
 

Is it OK to upgrade 311 to 435 in one operation?

At some point the website must switch from using ASP.NET 1.1 to ASP.NET 2.0

So I anticipate run the upgrade, then something will break at some point, change the IIS config to ASP.NET 2.0, and go back to recycle the web page that is throwing the error?

A second question ... I have a 435 install up and running. Cool in the HOST/Module Definitions section the different images to indicate whether your module is up to date or not. But sometimes there is nothing there. From one of my computers I always get the 'missing image' box with the alt-text (regardless of browser). On another, sometimes the images are there and sometimes there is nothing at all. Whazzup widdat?


pmgerholdt
 
New Post
10/23/2006 5:27 AM
 
I have done a couple of 3.1.1 to 4.3.5 upgrades with no major problem.

I recommend using this method to upgrade (this will preserve your 3.1.1 installation in case anything goes wrong):
  1. Make a complete copy of your DNN 3.1.1 folder in the wwwroot (call it DotNetNuke435 or something like that)
  2. Make a second copy of your DNN database (call it DotNetNuke4 or something like that)
  3. Look at this thread and run the queries I suggest against the new DOtNetNuke4 database: SQL Foreign Key Problem with 4.0.3 4.3.5 upgrade
  4. Download the Install Package for 4.3.5 and unzip into DotNetNuke435, overwriting files that are already there including web.config
  5. Edit the web.config in DotNetNuke435 to add your custom settings (database connections, machine keys, other customizations etc). Make the database connections point to the new DotNetNuke4 database NOT the original database)
  6. In IIS, change the properties of your DNN website so it is running ASP.NET 2.0 and the Home Directory is the DotNetNuke435 folder
  7. Browse your website and the upgrade process should complete successfully
If anything goes wrong you can switch your IIS site back to ASP.NET 1.1 and the original DNN folder. If you need to rerun the upgrade for any reason be aware that you will need to copy the ZIP files in the DotNetNuke435/install/modules folder from the Install Package again (the upgrade process deletes them after they are used).

I have no idea why those images are missing.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...311 to 435: Recommended path?311 to 435: Recommended path?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out