[NOTE:  This was originally posted at DevAuthority.com on 10/28/05.]Houston We Have A ProblemOk, we’ve all seen the .Net error pages that pop up in the browser just full of helpful information in debugging your application. Although useful (at times) to the developer, there is nothing more terrifying to an end user than filling out a form, clicking the submit button, and being presented with a Stack Trace. As developers, we need to be sure that these annoyances never reach the user. To achieve this we must implement good exception handling in our code....

[NOTE: This was originally posted at DevAuthority.com on 7/15/2005.]I just recently had a relatively new developer ask me how to raise events from a web user control to be handled in it’s parent form, so I thought it was worth posting here.  If you wish to be able to handle events in your code from user controls, it’s very simple:Step 1  Declare the event in your user control:            Public Event MyEventName()Step 2  Raise the event in your user control when you wish to have if fire:            RaiseEvent MyEventName()Step 3  When declaring your user control in...

[NOTE:  This was originally posted at DevAuthority.com on 7/19/2005.]I was recently tasked with applying some logic to an existing page where a datagrid was used to add and edit data.  This is nothing uncommon mind you, but I have (believe it or not) never used controls in the footer template.  The task involved determining whether specific controls were visible or not at runtime.  Since the footer template does not belong to the items collection I would be unable to see this using the EditItemIndex property.  After jumping through hoops I found that the...