I have a module I have "completed" and it is working fine the the VS 2005 (on Vista) environment.  I need to compile it to a dll.  I have tried to "Publish" it, but although the requisite .ascx files come out in their proper location, the is not a separate dll (or at least 1 I can recognize).  Any ideas on what I am missing?

I did follow the instructions at dotnetnuke.adefwebserver.com, but to no avail.  Hmm... WAP is configuring the module as a separate project correct whereas what I read in Michael's excellent article(s) was for "embedded" (i.e., non-WAP) developement?  Thus, the WAP format is in line with the "old" way to build the custom modules, i.e., separate projects?

Thanks in advance!

I reread the article and realized I combined it with some other posts... using WAP works fine to compile the module - not if I could just figure out why it is erroring in a non-dev instance of DNN (http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/276061/scope/posts/Default.aspx) *sigh*. Thanks for the pointers you two!