How to debug an installed module?  say forum module

A second solution that is quicker, though less thorough, would be to put the debug version of the dll and the symbol files (.pdb) in your DNN installation's bin directory. By doing this, you would get line number information in your exceptions when you view them in log viewer (or at the module's instance, if you're receiving exceptions there). You could use these line numbers to lookup exception sources within the source code without having to use VS 2003.

You could not make any changes to the source using this method. So ultimately it depends on what type of debugging you're wanting to do. If you want to figure out why your module is not executing properly, this might work. If you want to add functionality or make source changes, you'll need the full-blown development environment Erik described.

Hope this helps!

B

---

Brandon Haynes
BrandonHaynes.org