Yeah that's not doing it.  But I was able to convert another module so I'm sure you're right it's something in those two modules.  I don't know.  Thanks for the continued support.

So, Ryno has found a way for DNN4 WAP to DNN4 WSP conversion.

But what I am loking for is DNN4 WSP to DNN4 WAP conversion. Any automated method or tools available???

The reason I want to do this is because, I have found WSP approach better for development and WAP approach better for deployment. With WSP, I can modify the code-behinds without having the entire installation to recompile (off-course changes to App_Code classes need recompilation).

Although, I have not checked it, I believe that when you debug WAP projects by attaching to ASP.NET process, the source code files (including code-behinds) would be locked up by VS. In effect, you would need to stop the process, make the change, restart & re-attach.

I believe converting from WSP to WAP should not be difficult, as code classes from App_Code can be simply copied. I have no idea about what to do with control (ascx) files & code-behinds. Any idea Mitch??

If that Module Upgrade Wizard is open source and the code is provided I'm sure it could be updated pretty easily to do both conversions.....either way.

Here is a guide written by Mohsin and myself that we made to list the steps for converting WAP to WSP.  You might be able to use this to develop something?  I do think that's a good idea although I develop everything for my own website so I wouldn't need it particularly:

1. Create a folder called “DesktopModules” anywhere on your computer. In this folder, put your DNN3/DNN4 module source code (each with its own individual file name)….so in our case C:/DesktopModules/TeamPlayerBank
2. Run the “Module Upgrade Wizard”
   1. For the DNN3 input box browse to the DesktopModules folder created in Step 1 (this works even if it’s a DNN4 WAP folder so don’t worry about it being labeled as “Version 3” in the Wizard)
   2. For the DNN4 input box browse to the root of your local DNN4 install that you use for your coding environment
   3. Select “Next”
   4. Check the Module(s) you want to port over to DNN4 WSP format
   5. Click “Finish” and the browser will create the new WSP folders on your DNN4 local install and make several changes to the file structure (some info on what the wizard actually does can be found at the DotNetNuke website)
3. Rename ViewTeamPlayerBank.ascx to TeamPlayerBank.ascx
4. Rename EditTeamPlayerBank.ascx to TeamPlayerBankEdit.ascx
5. In the TeamPlayerBank.vb/Settings.vb/TeamPlayerBankEdit.vb files comment out all “'Protected WithEvents” from #Region"Web Form Designer Generated Code" or “Controls”
6. In the Dataprovider.vb file change the line “objProvider =  CType(Framework.Reflection.CreateObject("data", "Ryno.DNN.Modules.TeamPlayerBank.Data", "Ryno.DNN.Modules.TeamPlayerBank"), DataProvider)” to “objProvider = CType(Framework.Reflection.CreateObject("data", "Ryno.DNN.Modules.TeamPlayerBank.Data", ""), DataProvider)”
7. Use an existing WSP .DNN file and do a Text Search/Replace to reflect the “TeamPlayerBank” instead of the other module name or type up a new .dnn from scratch as is included in the “.DNN file” attachment (see below)
8. In the TeamPlayerBankController.vb and TeamPlayerBank.ascx.vb do a Text Search/Replace changing “Services.Search.SearchItemInfoCollection” to “DotNetNuke.Services.Search.SearchItemInfoCollection”
9. Make sure the “Constructors” stub in the TeamPlayerBankInfo.vb is not missing the trailing apostrophe which happens some of the time.
10. Compile in Visual Studio and fix any errors that might result for more complicated modules.
11. Run the existing SQL script to create the database/Stored Procedures
12. Import the Manifest (.dnn file) in the Module Definitions page (will be listed as long as there is a .dnn file in the DesktopModules/TeamPlayerBank folder