Am I the only one thinking that the limitation in DotNetNuke to only allow one extension/module per folder is quite stupid? I can understand the logic when you make public available modules that are to be redistributed, but for us making a large scale custom application it is quite frustrating. Just to give an example, we would like to have a folder under DesktopModules called "BackOffice" that would contain all modules needed for BackOffice, but because of this limitation in DNN we now have to create a whole lot of subfolders directly below DesktopModules like "BackOffice_Module1", "BackOffice_Module2" etc.

I recall from previous attempts that there was an index in the database that actually prevented you from having more than one module in the same folder (DB errors when inserting) which could probably be disabled, but without knowing any possible drawbacks of this, its not a desired solution. Is there another way to solve this? Or am I missing something obvious here? It doesn't really seem like there is an obvious reason why it wouldn't work with more than one module in the same folder, at least in a custom application.

This is what happens if you try to add modules in the same folder:

InnerException: Cannot insert duplicate key row in object 'dbo.Packages' with unique index 'IX_Packages'. The duplicate key value is (, MyApp_BackOffice.MyModule Module, ). The statement has been terminated.

Hello,

I guess I'm having trouble understanding what you're doing or why... 

You can have multiple modules in a single folder. It sounds like the error is coming from you trying to use duplicate package keys, which, as far as I know, you can't do.

A package is a set of additions to your system - often a module, for example. A single package can contain multiple modules - or other components. It sounds like maybe you mean to make a single package that has multiple modules.

If you want multiple packages, you can do that too, you just identify them in different ways.

Does that help at all?

Mike