Fiddler is the best HTTP debugger on the Internet. It monitors all web traffic and breaks down the data stream into a manageable and readable interface. You can manipulate data as it comes and goes, as well. You must have this in your toolbox!





Click here to download

One of my favorite Windows tools is Process Explorer by Mark Russinovich. This tools allows you to organize and break down Windows processes into an easy-to-read interface. It helps you keep an eye on what's going on, memory usage by process, and other great features. I consider this one of the main tools in my toolbox.

While binding an Asp.Net Repeater to a Datasource, the following error occurs when firing the OnRowCommand event. The simple solution is to exclude the binding process on postback. There are deeper explanations of the causes, but this seems to be the simple correction in the Page_Load event:

if (!this.IsPostBack)
     BuildInterface();

The error:

Thanks for stopping by the new JuddLink website. We're still working out the kinks, so please be patient with us.

Thanks again!

It always amazes me when an ugly application is thrown out because it's ugly -- not how it functions. Then, it's compared to a polished interface that is barely holding together at the seams. A total failure is somehow more forgivable if it is spewed from a clean, polished interface as opposed to a crooked bland layout. Developers are notorious for releasing interfaces that lack much of the eye-candy that most users take for granted every day. So, that leads to an important question: What do we really want in software? Who told us that a clean interface implied a functional system?