I've got a custom provider that I can install with a "package"-style installation manifest (type="Package" version="4.0") and it includes a type="Config" component to make changes to web.config. I need to do the same thing with a module installation. My module is a customized Roles management module and it needs it's own provider configured in web.config at install time. So basically, I've got a module that needs to have a provider installed and configured at install time.

I see a few approaches I could take:

1. Add a "config" element to the version 3.0 "module"-style installer. I don't know if this is even possible, as I can't find any documentation on the manifest schema.
2. Use a version 4.0 "module"-style installer. I don't know if such a thing even exists, as I've found no mention of it anywhere.
3. Use a different style of installer. I could use a "package"-style installer, but don't know if this is the right thing to do or if the rest of the module will be installed correctly.

Can you offer any advice or guidance in this matter?

Craig,

If you have tried option 3, it will be nice to know if it works for you.

I had a similar need in one of my projects.  I looked at the manifest file in the ActiveDirectory Authentication package and was tempting to use it.  I think only DNN 4.6 or greater supports this type of installation.  My project needs to support all DNN 4.X versions so I took a differennt approach.

When the module starts to load, the code checks if the required section is in the web.config.  If the section not existed, provide a button to write the section to the web.config.  MSDN has sample code to check/write to web.config.