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 ...Installation / Upgrade InstructionsInstallation / Upgrade Instructions
Previous
 
Next
New Post
6/15/2006 4:23 PM
 

In the latest release ( DNN 3.3 and 4.3 ) we have included the following packages: Source, Install, Upgrade, and Starter Kit ( DNN4 only ). I would like to share some info about these packages:

Source - contains all source code for the core framework. Includes a release.config and development.config file ( nop web.config ). Also includes Install versions of all Modules. If you need source for the modules, you can download them seperately from the download page on the site.

Install - contains just the run-time resources. Includes a web.config file. You should not use this version to upgrade an existing install unless you are very careful - because if you overwrite your previous web.config, you may lose access to your site membership. Includes Install versions of all Modules.

Upgrade - contains just the run-time resources. Includes a release.config and development.config. You can safely use this version for upgrading your site. However there is not automated utility for merging changes in the configuration files. Since there are nodes in the release.config and development.config which are new / required for DNN to function correctly, you will need to manually merge the applicable sections. This not a new step - it has been a requirement for any DNN upgrade all way back to version 1.0.0. Does not include any Module packages. The reasoning is that users do not always want to upgrade their modules when they upgrade the core.

In general, the standard method for dealing with config upgrades is to rename your existing web.config to web.config.backup. Rename the release.config to web.config. Then manually copy the following settings from the old web.config.backup to the new web.config file:

    <add key="SiteSqlServer" value="{connection string}"/>
    <add key="MachineValidationKey" value="{your localized key}" />
    <add key="MachineDecryptionKey" value="{your localized key}" />

you may also want to move your objectQualifier specification ( if you have one in your old web.config.backup )

    <data defaultProvider="SqlDataProvider">
      <providers>
        <clear />
        <add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="" databaseOwner="dbo" />
      </providers>
    </data>

Starter Kit - contains just the run-time resources. Includes a web.config file. This version is designed for software development activities. Contains Install versions of all Modules.

 


My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
New Post
6/16/2006 7:04 AM
 

And what if you get a System.IndexOutOfRangeExcepetion: Displayname

(I've seen more people who got this. I was doing a 4.0.3 to 4.3.0 with the upgrade version)

Server Error in '/' Application.
--------------------------------------------------------------------------------

DisplayName
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IndexOutOfRangeException: DisplayName

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

Stack Trace:

[IndexOutOfRangeException: DisplayName]
   System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName) +1358439
   System.Data.SqlClient.SqlDataReader.GetOrdinal(String name) +102
   System.Data.SqlClient.SqlDataReader.get_Item(String name) +12
   DotNetNuke.Security.Membership.AspNetMembershipProvider.FillUserInfo(Int32 portalId, IDataReader dr, Boolean isHydrated, Boolean CheckForOpenDataReader) +246
   DotNetNuke.Security.Membership.AspNetMembershipProvider.GetUser(Int32 portalId, Int32 userId, Boolean isHydrated) +43
   DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +799
   DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +83
   DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +3911
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

 
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

 
New Post
6/16/2006 12:43 PM
 
The keys shown in the first message are not like the validation and decryption keys in the Install download. (I'm not talking about the values, it's the key names).

Does it matter?

Here's what's in the download

    <machineKey
      validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902"
      decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"
      decryption="3DES"
      validation="SHA1"/>
 
New Post
6/16/2006 2:36 PM
 

hi

 I am installing dotnetnuke for the first time,and i am getting confused about what are we suppose to download .Do we need to download all packages ? I am not veyr sure about this, please help me out.If we have to work with dotnetnuke, then we will need all the packages ?

Pooja

 
New Post
6/16/2006 2:58 PM
 

you only need to download the package, that is appropriate for you:

  • if you only want to run a portal select installation package
  • if you are planning to develope modules or tweak the core use source version
  • if you want to make quick modules with VWD or VS2005, use the starter kit.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation / Upgrade InstructionsInstallation / Upgrade Instructions


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