Message to Bert and Vlado.Can you please contact me off-line (charles.nurse@dotnetnuke.com), so we can discus what needs to be done in the core to fully support using WAP for Module Development (as an alternative to the current method).
ie.
Module Packager - 3.2 and earlier included a Module Packager, that allowed a Developer to create the dnn file and zip file for distirbution. 4.3.2 has reintroduced this packager for WSP based modules. What needs to be done to extend this to provide a mechanism for packaging WAP modules (or is this best handled by Web Deployment projects and msbuild)
Module Upgrade Wizard - I created a simple WinForms based Module Upgrade Wizard for 4.3.2 so developers can convert their 3.x modules to the WSP development paradigm. What needs to be done to provide a WAP version (or option).
Installer - Is there anything that needs to be done to the Installer to support WAP modules
I have come to the conclusion over the last few months, that we (the core) should not be promoting one development method over another. Each method has its advantages, and each developer needs to make the choice that is right for them. Our (the core's) role should be to provide the tools to help them, whichever development methodology they use.
So far I have identified a number of development methodologys (in no particular order).
- WSP (dynamic compile) - the methodology used in the Starter Kit
- WSP (precompile) - Precompilation of the module and/or core (this needs a slight core change at the moment to use a different name than App_GlobalResources for the shared resource files, but I understand Phil Beadle has done this for a large site in Oz, and we are looking at making the change in the core, so this option is available.
- WSP + Class Library - Use a class library instead of App_Code (kindof a hybrid approach)
- WAP - Bert's/Vlado's approach