I ran into a similar problem -  custom module was fine on development box (VS2005) but failed with namespace ambiguities and null reference errors on test production server.  The only way I was to isolate the problem was to comment out increasingly smaller sections of .ascx markup (and any corresponding control references in the code files) and try install/run again until the problem showed up - at least that got me narrowed down to the problem area.  Another technique is to add in some Response.Write statements or send a message to a label control with appropriate degugging info. In my case, the problem turned out to be a reference to a method that I had not fully qualified as to its namespace. A core method of the same name rather than my method was being called.

BTW, are you using the dynamically compiled model for the module or is it set up as a WAP?

---

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

For anyone who's interested, I ended up calling "ProcessModuleLoadException" from the catch on all my methods rather than just in the Page_Load. That helped me locate the error, which was not showing up in my development environment because of the test data I had in the database.

All fixed and deployed now! Thanks for the suggestions!

Tim

---

--
Tim Rolands
Avastone Technologies | House of Nuke
Where DotNetNuke(R) Lives