Both the dynamic compilation model and the pre-compilation model work, but what I want is the VS2003 style pre-compilation of the module code into one assembly for all of the module's .ascx/.vb controls, one assembly for the sql dataprovider, and optionally additional assemblies for components, custom controls, etc. as needed rather than having to 1) pre-compile the ENTIRE solution and 2) ending up with a multitude of the hashcode appended .dll filenames that have to be located in the bin.
I though that preview releases of the VS2005 Web Application Project and Web Deployment Project would result in a posible solution to this request, but after spending the better part of a day trying different combinations, I ended up with the solution/project so fouled up that VS2005 would hang in an unending loop of " . . . sorry but this program must close due to a VB compiler exception" popup errors that even the task manager could not kill. Using a Web Application Project, I was able to compile as a separate assembly all of my components code that resided in the Web Application Project, but was not able to do the same for the codebeside files for the module controls that were located under the DesktopModules folder. I also had a difficult time resolving all of the references back to the DNN library, but was finally able to add them all into the project. When I tried the Web Deployment Project, I got the distinct (hopefully incorrect) impression that its use would require a total rework of the re-organization of the DNN library/website back to the VS2003 model. Not wanting to proceed in that direction, I gave up and just packaged the module following Michael's dynamic compilation model.
I posted a similar question here and in the DNN section of the ASP.NET forums a week or so ago with no replies - Has anyone figured out how to use the Web Application Project and/or Web Deployment Project to accomplish what many developers are asking for? It's sure beyond me!