Hi Austin,

I could be wrong, but I think one of the benefits of using the WAP model is that your VS project only contains your module's code. So every time you modify your module’s code and go to test it, you only have to compile the code from your module, not the code from the WSP DNN project that it physically lives inside of. Somebody please correct me if I am wrong about this.

Regarding resources for learning the method, there are MANY different resources both through google and on these forums. Just Search for WAP or on google: "WAP DotNetNuke". The problem though is that everyone seems to have their own variation on how they set up their dev environment and use WAP. So I think what you will need to do (and what I am currently doing) is to sift through several of these resources and figure out what works best for you.

I am not yet sure about debug considerations. I haven't gotten that far into my WAP setup yet J

Mitch:

I wanted to mention to you that you might want to consider working through you WAP method using VS 2008, as many people are probably going to be using it soon. Just an idea for your blog post…

I am a bit confused with this

"Using WAP you are compiling your module which helps catch bugs at runtime, You can still hook in the debugger to trap errors while running DNN, however, I never actually debug and step through my modules, as I haven't found a need to in all of the modules that I have built over my time developing."

I do not know a developer that does not like the ability to insert a break point into a project that is thousands of lines long so they can test... If you are saying you can just hit f5 and watch the code come to life with not a bug to trap then I need you on my staff... ; )

I want to debug in VS2005 with break points and hit F11 to move through the code.. what would be the best way for me to develop these modules with that in mind?

Are you saying that the WAP model is the only model that you can use to prevent distibution of your source?

Thanks

You can use this method:

Creating compiled assemblies

but using WAP for thsi is easier:

Using Web Application Projects (WAP)