Hi Lee

I have decided to install DNN 4.3.4 because I wish to use modules which are not available for DNN 3

I am not a developer so I downloaded the DNN install version with the intention of uploading to my hosting provider. When unzipped I found web.config, release.config and development.config.

I understand that I need to edit web.config and ( I read somewhere that I need to mirror the connection strings in development.config but I don't know why) and ignore release.config unless I am upgrading.

Am I correct so far?

The web config file contains an extra connection string:

 

<add

name="SiteSqlServer"

connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"

providerName="System.Data.SqlClient" />

--

<!-- Connection String for SQL Server 2000/2005>

 

 as well as the 

 

<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>

--

<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules>

Can you briefly explain the purpose of  these strings.

I know that I must edit accordingly:

Server=MY SQL-SERVER-NAME;Database=MY-DATABASE-NAME;uid=MY-USERNAME;pwd=MY-PASSWORD;"/

I am not having much luck trying to install my fresh DNN 4.3.4. I know that my hosting provider is currently using ms sql 2000.  I presume that my problem is with in the web.config file  but I can't find where I have gone wrong. With a little more understanding of this file I may be able to configure it correctly. 

Thanks

Regards

Lynn

 

 

Hi Lynn,

As it happens Andy Hock, a module developer, has put together an article for us looking at installing 4.3.4. As we speak i am also putting a series of videos for configuring the new security roles, user settings etc for 4.3 / 3.3.

For the web.config file you only use a single web.config file.

The release.config file is if you are upgrading, for transferring across your settings from a previous installation - which you rename to web.config

The development.config is used if you are required by your hosting provider to run in a medium trust environment. - If so, you use this file and rename it to web.config

If you are just installing from scratch and are not required to run in medium trust then just add your settings into the web.config file.

You only need to upload a web.config - do not upload the release or development.config files as they are not needed. They are just used as templates for you to use and rename to web.config dependant on your installation requirements.

The connection strings, you just set them up for SQL server 2000 rather than SQL server express. - So delete the express sections and just add in the details for SQL server, there are 2 parts where you need to add the details. - Your web.config may look like this on a localhost installation:

<connectionStrings>
    <!-- Connection String for SQL Server 2000/2005   -->
    <add name="SiteSqlServer" connectionString="Server=(local);Database=DNN434_Tutorials;uid=lee;pwd=lee;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
    <add key="SiteSqlServer" value="Server=(local);Database=DNN434_Tutorials;uid=lee;pwd=lee;" />
    <add key="InstallTemplate" value="DotNetNuke.install.config" />

Thanks,

Hi Lee

Thanks so much for your speedy and very helpful reply.

 

Regards

Lynn