In a compiled module (i.e. Web Application Project or WAP), all of your source code contained in the various entitiy classes, controller classes, utility classes, etc. and in the code behind files (.ascx.vb or .ascx.cs) gets compiled into an assembly (dll) which will ultimately get placed into the site's /bin folder.

It is still necessary to include in the installation package all of the .ascx files as they contain the html and .Net user control markup. I am assuming that you have placed all of the code associated with the .ascx files in separate code behind files (.vb or .cs). Other files which must be included in the package are those such as the .SqlDataProvider scripts, .resx language localization files, any custom image files, usually a module.css file containing any custom css rules, and any javascript files.

If you are using one of the compiled module templates with a MS Build script to automatically generate the manifest and the install package then I'm not sure what other assistance you made. The steps that I outlined were primarily for those not using an automated build process but is also helpful in generating a basic manifest that can then be modified if necessary and included in the automatically generated package.

Perhaps if you indicate which compiled module template you are using, I can be of additional assistance if you have further questions.

---

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