In all cases it should be the bin directory of the website.



I always have a small batch file which copies the files from my project build directory to my website bin directory.   I have many different versions of DNN under a common path, all with the same \website path.  Therefore I can run my batch file to copy from the project directory to the specified DNN version, which is essentially copy *.dll \dotnetnuke\dnnxxx\website\bin - repeated for the .pdb files as well.  I recommend this type of approach.  You can also hook this batch file up to your project build as a build step if desired.  This way you can quickly and easily test different versions of DNN (if needed, you might only be targeting a single version)



Doing it this way also helps to copy any other project related content, such as .ascx, .css , .js files - all of which needs to be copied to the DNN website as a package (and it saves having to build an install package and install every time).

Yes that's OK, but introduces a dependency between your module code and that database.  Just something to be aware of.

If the module contains more than just the bin file, remember you have to keep all of the files synchronised.