Hello, I'd like feedback on the methodology of iteratively testing DNN desktop modules during a full development cycle. I've been in ASP.NET development for a number of years but I'm just moving to DNN and I've found the pinned resources on this forum and other literature unhelpful on this one point. So I'd like feedback from experienced DNN module developers on how they go about testing. I see two approaches:

• If one develops a module as a standalone WAP project using the Starter Kit template, in order to iteratively test changes then the following should occur (1) the assembly must be built to the DNN website \bin folder; (2) manual or batch copying of user control markup must be copied over to the relevant website dir.
   
• Alternatively, one could (1) develop the module functionality within the main site (itself a WSP project) and when all testing is done, the user controls could be copied into a fresh desktop module WAP project for re-deployment elsewhere.

The two approaches do not cover SQL scripts and module definition as they're outside my concern; generally speaking for me, it is the markup, code behind, and utility classes that need continual and gradual changes, and hence continual testing.

So, what do you find is the least painful methodology?

Thanks for the link, that makes sense.