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

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesConnecting a Module to a separate database than the DNN databaseConnecting a Module to a separate database than the DNN database
Previous
 
Next
New Post
12/29/2009 9:13 AM
 

Hi,

I am in the process of developing a module and I am wondering how to have the module connect to a separate database from the DNN database that is installed. I have followed some procedures that I found through google trying to do this but my module is not using the correct connection string for some reason and is still trying to use the DNN database. The modifications that I have made so far are to the web.config file under Section group I added :

Code:

            <section name="claims" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />

under connectionStrings I added:

Code:

<add name="SQLServer" connectionString="Server=TempName;Database=Temp;User ID=exampleun;Password=examplepassword" providerName="System.Data.SqlClient"/>

and under <dotnetnuke> I added after the </data> tag

Code:

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

The only other modifications I have made are to my module DataProvider.vb for the CreateProvider to be the following, so that it uses the claims connection and not the data connections:

Code:

        Private Shared Sub CreateProvider()
            objProvider = CType(Framework.Reflection.CreateObject("claims", "Modules.Contacts", ""), DataProvider)
        End Sub

As well as a change to the SqlDataProvider to make under Private Members:

Code:

        Private Const ProviderType As String = "claims"

As said before this will not use the correct Database when I go to the website. Am I missing something in my connection to the database?

Thanks,

Chris

 

 
New Post
1/6/2010 11:52 PM
 
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesConnecting a Module to a separate database than the DNN databaseConnecting a Module to a separate database than the DNN database


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