I havent used "Create Module Package" for a while but as I am going to convert some modules I did today.

I found that the package was created in Install-Modules and didnt understood why, its hard to get it there if you not on your own server. But ok its good if you like to install the module again after deleting it of cource. So I did a simple test deleted the document module and reinstalled the module again. Now I discovered that the bin was not in the file neither in the dnn file. So I have to get the bin from an other source.

So my questions.

Is this a bug?

If not does the function work for version 4 modules?

Should it work for ver 3 modules?

What are the reson for putting the file in INSTALL folder?  (if a bug there could bee)

Thanks in advance

Jan

Hi Sebastian,

Now you know one! The server where one module is located in Singapore. I develope my modules in Sweden. I havent developed the module from begining. The world are not black and white, I think I can get the information anyhow but for me its an issue right now.

Regarding Relese 3 modules I didnt get any answer I think, I just tested to make a package from Blog module 3.3.0 and the package does not include any bin file.

And all other rel 3 modules have the same behavior. Have you tested it resently?

Could you please test once more, I have the same behavior in all 4.7 and in a 4.4 installation as well. No bin file (dll) in the package.

If my tests are correct, and I think they are, there is a bug. Rather dangerous now then the file are in install folder. (even if the sheduled installer does not work but that part I havent test in 4.7)

Jan

Jan, packaging of DNN 3 modules in DNN 4 is not supported - you cannot compile it on DNN 4 and it is assumed, that packaging takes place on the development machine.