Michael Washington explains in detail the steps required for packaging a module at:

http://www.adefwebserver.com/DotNetNukeHELP/DNN_PackageModule/Default.htm

However, there are 2 points that are missing from that tutorial:

1) The DLLs are created Folder wise. That means dll for code-behinds in DesktopModules & App_Code files are generated separately. And if there are sub-folders in the main module folders, they again have separate assemblies generated. But I have seen modules (including those shipped with DNN) have just 2 assemblies, the main logic assembly (including code-behinds) & the SqlDataProvider assembly??

So, how can I achieve the same, while preserving the folder structure of my module (or would I need to put everything in the same folder)??

2) I don't want to provide my clients with the ascx markup. So, if I create my assemblies without the following option:

Allow this precompiled site to be updatable

Would it be possible for DNN to pick up my module controls from the assembly. If yes, then how should I provide the control entries in the & section of DNN configuration file for my module???

I am using VB. And I dont know what is WAP or WSP development method. Can you explain a bit more???

As I pointed out above, I dont want to provide my clients even with the ascx markup.

Is it possible for DNN to pick the controls from assemblies, if I compile them using 'Not Updateable' option???

I get the following error while creating a compiler assembly project:

"The Project Path 'Path to temp files in local settings\myproj.vbproj' could not be opened.

The Project type is not supported by this installation."

What now?? I have the starter kit installed properly in my VS installation??

Okay, I am searching & finding some things out!!!

Does the WAP coding model support modify & continue approach of code-behinds supported by WSP???

I know this is going over the board ith questions, but Mich, you always have been very supportive

Is there any automatic way or tool to convert controls coded using WSP to WAP controls??

I mean 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, and put up a question for this above (that is still unanswered), I believe that when you debug WAP projects by attaching to ASP.NET process (read your blog on debugging WAP modules), 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??

Mitchel, at the following thread on DNN forums:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/231158/scope/posts/Default.aspx

Wes Tatters tells me that WASP project files can be converted to a WAP project by simple copy (ensuring that none goes to App_Code folder. Is that true & so simple for converting a WSP module to a WAP module??

If that's so, then I could not understand all these discussions among developers (including between you & Michael on DNN Forums) on which approach should be used, or is best.

There is no doubt about WSP's RAD & debugging advantages, and WAP's deployment ones. I would always develop my modules as WSP. Then, when they are complete, create a new WAP project, and add the existing files using 'Add Existing Item' option from VS context-menu appearing on right-clicking a Project node in Solution Explorer. That would further avoid copying effort & duplicate code-base.

As I have never done this before, and today was my first tete-a-tete with the WAP approach, would my technique work, and is there any problem with this approach???

Mitch, I would request your kind comments for the following thread:

www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/231158/scope/posts/threadpage/2/Default.aspx

And there are only 2 issues remaining now:

1) Does DNN allow complete compiles including markup (i.e. can it pick-up the ascx markup from compiled assemblies)???

2) For converting to WAP, I need to create a .designer.vb file for each ascx file. Do you know of any automated tool to do that???

Thanx!!!

Finally Mitch, I have been able to get everything through!!! And I greatly acknowledge your support together with support at DNN Forums in helping me & others out. Keep up the good work man... And Thanx a ton.

This is how I got everything through:

1) Just copied everything from WSP to a entirely new WAP project, that was in its own solution outside DotNetNuke solution.

2) Used VS to convert it into WAP (mainly the generation of designer files)

3) Here again, I was stuck. I could not found an article explaining deployment of a WAP module. I kept expermimenting for the last 3 hours, and now have it through.

Basically, just publish your WAP module by right-clicking its project name, make a zip file containing necessary resources (.ascx, .dlls, .resx & off-course .dnn). Finally, upload the zip to DNN in a standard way.

Is their any problem with the above process Mitch???

If not, I would always do it this way. Develop as WSP & deploy as WAP. I must say deploying as WAP also has another advantage. With WSP, you need to publish your entire DNN installation, and then pick up tour files from the compiled files. The DNN installation in itself can take a while to be published. But with WAP, this is a breeze.

THANX AGAIN MITCH

Yes, I also tried creating a "build.bat" file, and asked VS to execute it as as a Post-Build event after a successful build. And that eased things further...

BUT!!! Really had to recall hard all those command prompt syntax for using variables, concatenating, echoing & all that. It was certainly worth the effort

Mitchel,

Kind of on topic almost...

Do you know if there is a way you can have your dotnetnuke module project stand alone? I want to be able to check my module project into source control without having the whole dnn website also in the solution (and thus also in source control).

I've tried creating its own solution but running and debugging it is wanting the module to have its own virtual directory. I tried telling it to use the main dotnetnuke web site as it's main url but still no luck. Feel like i'm close but can't seem to get it to work.

thanks in advance,

Stephen

I almost do it this way now.

I develop my projects using WSP model (for greater productivity), and distribute them as WAP (for easier distribution).

I am able to convert a WSP project into a WAP project inside 5 minutes now using some DNN support projects I have developed for myself.