To expand on Michaels comments there will always be two options as long as ASP.NET allows complied and source versions of code to be used to deploy a site.

I use WAP to get the ease of source control integration, compilied assemblies and the ability to distribute NON source code versions of modules, which is a must do if you are working with a commercial prodct.

As for the translation process, it is pretty simple to implement the changes needed to clear out conflicting files on install.  As Michael mentioned you need to create a .txt file listing all files to be deleted.  If you want to see an example of this, you can download my Guestbook module from http://www.mitchelsellers.com for version 2.0.0 I did the migration from WSP to WAP.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Souce control is also easy with WSP. See: Using Source Control with DotNetNuke

---

Michael Washington
http://ADefWebserver.com

A Free Open Source DotNetNuke Help Desk Module

So now I have some DNN4 WAP PAs and associated source code and I want to take those and convert them into WSP on my local machine (and then I can use the Create PA inside of DNN to make an actual WSP PA from what I understand).  I have a clean install that does not have these PAs on it yet.  I would guess there is no reason then for that install to use the .txt file mentioned to remove any DLLs because they don't exist there.  But how to get those PAs up and running in my local environment in a WSP format is the question.

I am running my local DNN install as a Web Project (no solution file) and didn't download the DNN Source installation.

I create a folder for the module in the App_Code section and put in my DAL+ .vb files and the I create a folder for the module in the DesktopModules folder and put in the rest of the files (no .dlls).  Is there anything else that has to be done?  My module doesn't compile correctly so I assume I'm missing something.  I get a ton of errors and warnings and Global.asax comes up several times.  I must be missing something.

---

I'm too poor for anything other than the community version