Try using the Module Upgrade Wizard

---

Michael Washington
http://ADefWebserver.com

A Free Open Source DotNetNuke Help Desk Module

I just checkec out the wizard.  It appears that is for DNN3 modules in a DesktopModules folder of an installation that ports it to a new DNN4 installation.

I have working DNN4 WAP modules (and the source code files) and one DNN4 installation.  I'm just wondering how to get those DNN4 WAP PAs into WSP on my one existing local DNN installation.  The upgrade wizard documentation gives some clues.  It appears altering the web.config with a SubDirectory node is suggested/required even for vb.net modules.  I would assume that since my DNN4 WAP PAs work without error that if I were to port them over to WSP they should compiled without error?  Is that a correct statement?  Or does something other than moving files into the two folders and updating the web.config need to be done?

---

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

My comment about SCC being easier with WAP is that with WSP you only have 1 parent node in your source control system, all modules etc are under the same tree.  With WAP you can create individual trees for each module to isolate everything.  For my purposes this is good so that I can develop modules for myself and clients and store them in separate Source control repositories.

---

-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