Nothing of interest? You must not be reading then :)

As the first one says it helps you move DNN 3 modules to WAP modules. The second one guides to create WAP modules from zero. Both are approaches to produce dlls from your code.

Actually Partial Compilation is the term for having all the code behind / code beside code compiled at run time
- which by default IMPLIES that the .vb files need to travel with the module.

There is a workaround for this writen up by Michael Washington 
- but it is a little messy and involves having1 DLL per aspx file
- it is also gets pretty ugly when you try doing updates.

http://www.adefwebserver.com/DotNetNukeHELP/DNN_PackageModule/Default.htm

Westa

Westa, that is called Dynamic Compilation. I have yet not seen any official reference to Partial Compilation in Microsoft sites, but I've seen it mentioned in severeal other places, including forums.asp.net where I am a moderator.

Based on what the OP wants, -check his i.e. in parenthesis in the first post-, I assume he's looking to deploy his code in a dll while the UI remains in separate files, which falls within the description of what a Compiled Module is in the Dotnetnuke domain. Although packaging each file as a dll also produces dll's, it fails to produce controls and pages that can be distributes as they are only stubs. Hence my emphasis on WAP in the replies. I favor WAP but that's off-topic.

Anyway, to the OP: If you've developed modules in DNN3, -which are all compiled modules, you can still use the same approach by using WAP (web Application Projects) and package it as an installable PA. I honestly  do not understand what you don't understand. So maybe we can start from the begining again.