I may be missing something here, but why isn't the source for DotNetNuke distributed as a web application project, rather than a web site project?

Isn't a web application project much more suitable for a project the size of DotNetNuke? and it would work the same way that it did in Visual Studio 2003, i.e. I would be able to add the DotNetNuke web application project to my existing module solution, and reference it as a project reference, and exclude it from the build.

Christ, I am a bit behind! 

It seems that the only reason for using WSP rather than WAP is to cater for people developing with VWD.  It would be interesting to find out what percentage of module developers are using VWD over VS2005.

Thanks for the links, but I already use a method which I used to use under VS2003.  I create a new solution for my module, and then 'Add Existing Web Site', add the DNN web site (which I build with the starter kit), and then exclude it from the build.  To add a reference to DNN, I use a file reference to DotNetNuke.dll, and set copy local to false.

Then I have a post-build event which calls a batch file which copies all the dll's, ascx, resx, and any other module files to the DNN installation, and also builds the installation zip file.  This allows me to have decent .dll names.

This works pretty well, but would be even quicker I'm sure if DNN were a WAP rather than a WSP, then I could use a project reference, rather than a file reference.

Are there any plans to provide DNN as both a WAP and a WSP?