You cant really test a module unless its running inside dnn and interacting with all the elements of the site -- not to mention the classes it extends from.

But of course you can debug a module running as a part of dnn - firstly how do you have your module setup.

Is it in its own solution (Web Application Project) - or is it a set of files in the /DesktopModules/ path using dynamic compilation (Web Solution Project).

If its a WSP you can just open your website inside Visual Studio, set breakpoints on your code and hit debug.
- if you want to edit code - make changes and save code 
- refresh the page with the module - new code will be automatically updated

If its a WAP you will need to open your solution in Visual Studio
 - compile the module in debug mode
 - Install Module - copy the lastest version of your module files onto your local test site /DesktopModules/myModule/ etc
 - making sure the debug .dll goes into the /bin/ folder - not a release version.
 - wait for asp.net worker process to restart (this is needed because any file that is changed in the /bin/ folder will force a restart.
 - then while the process is still running use the Debug-> Attach option in  Visual Studio
   this will attach the debugger to the running asp.net worker process w3wp.exe.
 - you should then be able to again set breakpoints in your code.
 - If you want to edit your code - repeat the process 

Westa

PS - will someone remind me again why WAP is so good for development

hello 

you can follow this link to learn how to debug your dnn code

http://www.youtube.com/watch?v=2EHldD...

thanks 

manish singh