I have a set of modules that I have been developing for a few years for a specific site.  I am now trying to build a PA so that I can more easily distribute the module to other sites and for my own ability to keep track of versions.

The modules were developed prior to the Packages concept and were individual modules but all resided in the same DesktopModules folder and use the same Dataprovider and I have recently set up a web application project to get a single dll.   

It appears to me I can package this up with a single package that has multiple module components in it.  This lets there be a single install and uninstall point and the individual modules can be placed on separate pages as I intended.  However when using the "edit" of the extensions, there doesn't seem to be any way of displaying anything but the first module component in the package.  I currently have this running in my development environment set up by using a sql query to updating all of the desktopmodule records to point to the same package.   I get the individual modules in the dashboard dropdown but otherwise can't see them through any interface in DNN.

If I put them all in different packages in the manifest it seems to me that they will uninstall individually, potentially breaking something or at least not correctly uninistalling.  At any rate, I don't intend for the modules to be separately removable.

Is anyone aware of this gap in the extensions interface?  Am I doing something horribly wrong by having multiple <component type="Module"> in the manifest? 

---

Jeff Martin
MCSD C#

What I have seen when I combine the modules into multiple module definitions under the same component, is that all of the modules drop on to a page when I add it.   I don't want my users to have to remove 6 modules from the page when they really want just one.  Let me know if I am doing that wrong.

The other downside of there not being a clear interface for multiple components/modules under one package is that I can't control setting some of them to Premium.  I only want certain of my modules to be accessible to all portals.

So just to clarify what I want:  If a package/extension has several components, I want access to edit them all.  I want to set them individually to premium or not.   I want them all in install together and uninstall together.

The database structure of DNN supports this, the manifest structure of DNN supports this, the admin extension module interface does Not.

---

Jeff Martin
MCSD C#