Hi all,

I'm a DNN newbie, so bear with me.

I'm using DNN 5, and am developing an internal reporting solution that uses custom modules on different pages - for example, the Reports page has a "Reporting" module that displays reporting information, the Charts page has a "Charting" module that displays charts, etc. Each of the modules requires its own ascx control(s), but shares the same common library code.

Is it possible to package all of this into a single package, defined within a single .dnn manifest? If so, how?

I've got the installation working fine with a single Module, but when I specify a second <component> element for a second module then the package installs successfully, but then when I navigate to a page I get a module load exception:

DotNetNuke.Services.Exceptions.ModuleLoadException: An entry with the same key already exists. ---> System.ArgumentException: An entry with the same key already exists. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.SortedList`2.Add(TKey key, TValue value) at DotNetNuke.Entities.Modules.DesktopModuleController.GetPortalDesktopModules(Int32 portalID) at DotNetNuke.UI.ControlPanels.IconBar.BindData() at DotNetNuke.UI.ControlPanels.IconBar.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

I don't know whether it's possible to do what I want to do with the new manifest file, or whether I need a separate package for each Module - in which case, how do I handle the common code (they use the same dlls)?

Any help or insight you can provide will be much appreciated.

Kind regards,

Peter.