Hi there fellow DNN lovers,

I was hoping that someone could help me out here.
I would like to know how (I assume it is possible) you step through code when debugging a module.

At the moment I upload the module to my Dev Env and wait for it to fail, then "find" the error by a number of techniques, mostly time consuming.
I would love to be able to step through the code like you would a Windows application.

Potentially expanding on this post would help a lot 
http://www.dotnetnuke.com/Resources/F...

Thanks so much, appreciate your time and concern.

Cheers

Craig

Hi Sebastian, Thanks for the reply. Just to clarify: I should put the Debug Symbol Files, ie. .pdg files into the Root of my local DNN install? eg. My Local IIS Instance points to E:\DNN55 so will put the pdg files into E:\DNN55\bin? In web.config I have altered this line to debug="true" I guess I am wondering how the compilation connects to visual studio still? Should I move my entire solution to this directory somewhere? If so, should it go into the DesktopModules\myModule folder for the item I am working on, or should it be in the Root dir of the website, or am I kinda missing the point? What if I created an App_Code directory in the DesktopModules\myModule or use the one in Root and drop the .vb or .cs files in there? Then open the entire DNN instance in Visual Studio in order to set the breakpoints at the relevant module lines I want to develop/ check. I appreciate your time and expertise. Thanks C

Thanks Sebastian, Appreciate your help. The only thing I would add to help the next person is that you need to be running VS in Administrator mode in order to attach to this. Also setting the ping settings in IIS on your Dev machine to false as per this link http://msdn.microsoft.com/en-us/library/bb763108.aspx to enable debugging over longer periods of time. Thanks