Can someone please tell me if there is a reason for the IX_Packages in the Packages table, or rather, that is has been set up like it has?  If you do some searching for IX_Packages, you will see that a lot of people are having problems with this, and who can blaim them, unless you know your way around SQL Server and indexes, you wont have a clue what is causing this.

I've seen some people respond something like "every module must have a unique name" which is fine, but what actually gets stored in the "Name" colum does infact seem to be the name of the containing folder instead. Yes, there are some other columns in the index as well, but I would guess they are all the same for most users.

By using the folder name to where the modules are located, it makes it impossible to have more than one module in each folder, is there an advantage to this that I am missing or is it just bad design / a bug? Considering that DNN doesnt seem to support more than 2 folder levels under Desktopmodules, it forces you to create some very odd folder names, and also, lots of unnecessary folder. Or am I missing something here?

What are the reasons for this, besides the Index prevents it? I could be remembering wrong here, but I am quite certain that I have tried modifying the index before so that DNN wouldn't crasch when I try to add more than one module and that it worked without problems. This was some time ago though...

If you want to create a module using multible module definations it is possible to be done.  You have to create into the menifestfile for each moduledefination a own section.  You have to named the the moduledefination unique, this means you can have Modulename1 and Modulename2 in the moduledefinations but you can't use the same name!

Also you could run in some settings issue, and you must have a setting wrapper or create one Settings class with specific Load and Update Methodes for each dmodule Defination.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN