Debugging DotNetNuke using a custom TraceListener

[Reprinted from www.theaccidentalgeek.com]

One of the main debuging tools for most developers is the liberal use of debug, trace and assert statements in their code.  The use of these classes can provide lots of useful information to the developer during both development and in the production environment.  Microsoft has optimized these classes to minimize the performance impact when no TraceListeners are present.  So knowing that these classes are useful for debugging misbehaving applications, how can the DotNetNuke developer take advantage of these classes, even in a production environment?

In his blog on November 8, 2005, Victor Vogelpoel presented a webpart which will register a tracelistener and then display the trace messages.  When I saw this, the wheels immediately started turning.  Why could we not have the same thing for DotNetNuke?  So I spent a couple hours today converting Victor's code to VB and modifying it to work in DotNetNuke.  I have included a PA and will release the code at some point once I have documented it a little better and added a few features which have not been fully implemented (still need to add category filtering).

Just drop this module on a page and you will be able to see any messages that were added during the current request.