Is there any way to generate multiple assemblies for a single WAP project??

Let me explain why I want to do this. I am developing custom modules for DotNetNuke. For avoiding to distribute code-behind, I use the WAP model for development. Also, I do not create my WAP projects inside DNN solution. Instead, I have my own solution, named DNN, which contains independent Module, Provider or Skin projects for DNN.

All such projects reference needed DNN assemblies. This time I had a new situation. I needed to use code-behind classes of DNN controls, that have been developed using WSP model. As these classes were not available as compiled assemblies, I simply copied them to my project & built my project. However on deploying it into the bin folder, it produced (un)expected Ambigous class errors, as those DNN code-behind classes were present both in my assembly, as well as were dynamically compiled from the DNN source-code present.

So, what I want to do now is to have some way, so that my WAP project produces 2 assemblies, one containing only my custom module classes, and the other containing the DNN classes I copied to my project. Thereafter, I would only deploy my assembly, which would get the required referenced DNN classes from the dynamically compiled DNN code...
 

I have a bit of a change in what I am trying to accompolish. Now, I do not want those DNN classes I have copied to my project to be compiled at all. What I am looking for is that only my classes get compliled into the resulting assembly, and nothing is created for DNN classes. To put all this more clearly, is there any way to exclude some classes in a WAP project from compilation, so that they are not present in the assembly generated after compilation??

You've got to break the assembly barrier.

Put whatever classes you don't want compiled in your WAP Project assembly into a separate Class Library project and reference it from the WAP project. Both projects can coexist in the same solution.