Austin Henderson wrote
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
Yes, I am saying that in all my time coding DotNetNuke Modules I personally have never needed to run in debug mode and set breakpoints. Granted I have had errors, but the exceptions tell me enough to fix anything that comes up.
Michael Washington posted a few good articles on how to attach the debugger to a running process, to debug running code.
Also, you can create compiled assemblies with WSP, but it is much easier with WAP.