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 ExtensionsProvidersProvidersModify web.config when the module is installedModify web.config when the module is installed
Previous
 
Next
New Post
9/22/2011 5:39 PM
 
Can anyone comment on this new (as of DNN5) functionality that I found in the post: http://dnnsitemap.codeplex.com/workit... ?  The post says that this feature has been added: "DNN 5 provides a way to modify the web.config as required by the module at install time.  Add the feature so there's no manual setup involved".

I have not been able to find any other discussion or documentation on it or how to use it.

Brilliance Business Solutions | Manufacturing E-commerce
Use AspDotNetStorefront with DotNetNuke in a way that is seamless for the end user.
Learn more at InnestoNuke | DotNetNuke E-commerce
 
New Post
9/22/2011 9:11 PM
 
You can do it like this. 
<component type="Config">
  <config>
    <configFile>web.configconfigFile>
    <install>
      <configuration>
        <nodes>
          <node path="/configuration/configSections/sectionGroup[@name='dotnetnuke']" action="update" key="name" collision="ignore">
            <section name="clientcapability" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
          node>
          <node path="/configuration/dotnetnuke" action="update" targetpath="/configuration/dotnetnuke/clientcapability" collision="ignore">
            <clientcapability defaultProvider="WURFLClientCapabilityProvider">
              <providers>
                <clear />
                <add name="WURFLClientCapabilityProvider" type="DotNetNuke.Services.ClientCapability.WURFLClientCapabilityProvider, DotNetNuke.Provider.WURFLClientCapabilityProvider" />
              providers>
            clientcapability>                  node>                 
        nodes>
      configuration>
    install>
    <uninstall>
      <configuration>
        <nodes>
          <node path="/configuration/dotnetnuke/clientcapability/providers/add[@name='WURFLClientCapabilityProvider']" action="remove" />
        nodes>
      configuration>
    uninstall>
  config>
component>


Philip Beadle - Employee
 
New Post
9/23/2011 10:15 AM
 
Thanks, Philip!

Brilliance Business Solutions | Manufacturing E-commerce
Use AspDotNetStorefront with DotNetNuke in a way that is seamless for the end user.
Learn more at InnestoNuke | DotNetNuke E-commerce
 
New Post
9/24/2011 2:52 AM
 
FYI the wiki has full documentation for all the manifest settings - http://www.dotnetnuke.com/Resources/Wiki/loc/allpages/Cat/Manifest.aspx . The Config page gives a breakdown of how it works and a few further examples thougn I think the example Phil gave probably gave you all you needed to know - http://www.dotnetnuke.com/Resources/Wiki/Page/Manifest-Component-Installers-The-Config-Component.aspx

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
10/24/2011 10:28 AM
 
Hi,

Does anybody have an idea of the exact syntax (or working example) of manifest file referencing external configuration file?
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsProvidersProvidersModify web.config when the module is installedModify web.config when the module is installed


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