Hi.

I'm new to DNN custom modules.  I created a module that needs to access multiple data sources.  The code all works great, but now I want to package it so I can deploy it on multiple DNN sites.  I was able to create the package very easily from within DNN.  However, I can't figure out how to get the package to modify web.config to add new database connection strings etc...  I noticed that the package that DNN created did add a line in web.config to let .Net know that my module was written in C# rather than VB, so I would think there would be a way to do this.  If anyone could point me in the right direction, that would be great!

Scott

We have used structure like this:

    string WebConfigFileName =
     Server.MapPath(Request.Url.AbsolutePath).ToLower().Replace("default.aspx","web.config");
    System.Xml.XmlDocument objDoc = new System.Xml.XmlDocument();
    objDoc.Load(WebConfigFileName);
    System.Xml.XmlNode objHttpModules = objDoc.DocumentElement["system.web"]["httpModules"];
    bool Exists = false;
    foreach(System.Xml.XmlNode objNode in objHttpModules.ChildNodes)
    {
     if(objNode.Attributes!=null)
     {
      if(objNode.Attributes["name"]!=null)
      {
       if(objNode.Attributes["name"].Value=="OurName")
       {
        Exists = true;
        break;
       }
      }
     }
    }

    if(!Exists)
    {
     System.Xml.XmlNode objAdd = objDoc.CreateElement("add");
     
     System.Xml.XmlAttribute objName = objDoc.CreateAttribute("name");
     objName.Value = "OurName";

     System.Xml.XmlAttribute objType = objDoc.CreateAttribute("type");
     objType.Value = "OurValue";

     objAdd.Attributes.Append(objName);
     objAdd.Attributes.Append(objType);
     objHttpModules.AppendChild(objAdd);

     try
     {
      objDoc.Save(WebConfigFileName);
     }
     catch(Exception Exc)
     {
      DotNetNuke.Skin.AddModuleMessage(this,"web.config updates error "+Exc.Message,
       DotNetNuke.UI.Skins.Controls.ModuleMessage.ModuleMessageType.RedError);
     }
    }

Hope it helps.

Sergey

Hi Sergey,

Thank you for the reply.  All of your code here seems to make sense, but where does it reside such that it gets invoked when the module is being installed?  Thanks again for the response.  I really appreciate your help.

Scott