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.
The WSP model is not far easier to configure and use, its the same, but I'm sure it is also slower than a WAP model would be.
I do not know of any plans to make a WAP version since you are able to use WAP with DotNetNuke right now.
I think it would help if you would go through the tutorial. Build a project and then indicate where you felt the new development is lacking. The new method is faster and easier. I have used both methods for years and this is simply the truth.
Please understand I do not wish to change your prefered way of developing. I am simply reponding to an impression that DotNetNuke is not providing the best development environment possible.