Although I don't usually deploy a module this way (using instead the Create Module Package available on the Host-->Module Definitions tab), it should work for a dynamically compiled module (as indicated by your mention of the App_Code folder), provided you are very carefull to transfer all the files, set up the sql tables and sprocs, AND check that the module definition matches on both the dev machine and host.

That said, check that if the module's App_Code subfolder is referenced in the CodeSubDirectories node of the local machine's web.config it is also referenced in the CodeSubDirectories node of the host machine.  This is a must if the module is written in C# rather than VB.

I'm wondering if the exception is not related to the method used to move the module to the host machine, but rather due to a problem that is revealed in a slightly different environment, but as the exception is a very general one, could tell better if you post the complete exception (particularly the stack trace) that you will find in the Event Viewer. What are the differences between the two installs - DNN version? databaseOwner or objectQualifier attributes? Culture? other dynamically compiled modules, etc.??

 

---

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