A good practice that I'm using when working with ASP.NET controls that saves me a lot of work.

Some guidelines for .NET Framework designs

The all-useful CancelEventArgs, a common pitfall with using it and a safer alternative.

Article that describes how events are implemented and what happens if you forget to unhook the handlers.

The difference is that throw; preserves the original stack trace and throw ex; truncates the stack trace below the method in which the throw ex; call is located.

A description of a common pattern for working with DataReader object which as described here: http://vaultofthoughts.net/WhatYouShouldDisposeWhenUsingADONET.aspx Is IDisposable and should be disposed!

The alpha release of the ASP.NET Best Practice Analyzer was about 5 weeks ago. Similar to the popular SQL Server BPA, the ASP.NET BPA evaluates a set of best practice rules and tells you about configuration problems in your applications. The tool checks both machine level and application level confi...

After you have decided when you need to throw exceptions, the next step is to pick the right type of exception to throw. This section provides those guidelines.