Hi all

At the moment I'm seeking for a fitting deployment strategy for my DNN Applikation.
Problem is:

We're going to develop a bunch of different modules for our DNN-Application. The modules will be independently from each other regarding the business-scope, but they'll share the same libraries and will be implemented against some additional internal framework.

The whole problem breaks down to put some .dlls like "myCompany.Shared.Utils.dll" and stuff into the bin-folder of my DNN-Application.

Let's assume that those libraries are ready implemented and won't change (ok - that's very optimistic...). What then is the best way to get those libraries into the bin-folder ? Packaging them into the module installation package works while installing them but not when uninstalling because then they'll be deleted again.

Creating a dummy - module which like "framework" which only contains the libraries, and creating the concrete module packages without the libraries ?
Or is there a trick for the modules definitions ? Or just simply copy them into the bin folder on FileSystem/FTP - side without any module definition ?
Or any other strategy ?

Thanx in advance
Bernd

I think if the module only contain the library, you can't publish it as module since it will be on Modules table and load into the module dropdownlist at DNN control panel. You should put those libraries on BIN at DNN root using another technique such as FTP. But if you have no access to FTP, so yes the module approach is the only way.

In the latest DNN version, you can upload your module and can uninstall it WITHOUT deleting it's files. So the library will be safe at you bin folder.

CMIIW.