I believe the problem lies in that your module is set up as a Website Project (WSP) or dynamically compiled module having source files located under the app_code folder AND also has a couple of DLL files in the /bin folder. When creating a module package, the PAWriter takes very different branches in determining which files to include in the package depending whether the module is set up as a WSP or WAP (web application project). The branching decision is based on whether a *.vbproj or *.csproj file is found in the module folder. If a project file is found, the assumption is made that this is a WAP and that the projects DLL's located in the /bin folder will be included in the package. If no project file is found and code files are found under the app_code folder, no DLL's will be included in the package.

I'm not sure if this is entirely by design or oversight that dynamically compiled modules may need to include other DLL's as specified in a manually constructed manifest. At any rate, you will probably have to manually add the DLL's to the package.

It appears that the new universal package installer will be able to handle this when DNN 5.00.01 is released. I also recall that there were still some related issues with package writing in 5.00.00.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

@Bill - Thanks for the explanation.

@Bruce - Amazing how great minds think alike!  That's a near perfect description of how I am currently working.

Thanks guys.

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk