The problem with calling Validate in Page_Load is that your controls may not be ready to be validated (i.e. they need to be Loaded before they are ready to be validated).

Quoted: One potentially confusing thing about this timing is that the validators will not have been evaluated at the time Page_Load is triggered. The benefit of this is that it gives you a chance to programmatically change property values affecting the validity of the page, such as enabling or disabling certain validators.
...
If this timing is not to your liking and you prefer to evaluate everything in Page_Load, you can do this by explicitly triggering the validation during this event by calling Page.Validate.

Some nice .Net "Cheat Sheets"

Overheard our officemates talking about this.

Quoted: ScaleOut Software provides powerful distributed caching for enterprise ASP.Net applications running in server farm or grid computing environments.

Nikhil just updated Facebook.NET.

Quoted: A quick update on the release of Facebook.NET 0.3 with support for new and changing Facebook APIs...

It's good practice to avoid making database or remote calls in a static constructor. If the call throws, the type will fail to initialize, and you're out of luck for the duration of the application lifetime. We've been hit by this a few times.

Quoted: A TypeInitializationException can be a fatal error in an application since it renders a type useless. You should plan to catch any exceptions inside of a type constructor if there is any possibility of recovering from the error, and you should allow an application to terminate if the error cannot be reconciled.

This is pretty good for an Internet Explorer-based tool.

Quoted: A browser extension to provide tools for the Web developer including ASP.NET page and control developers.
...
# Ability to view items stored in cache, and remove them for testing purposes.
# Ability to shutdown the application (unloading the associated appdomain), in order to test starting it from a clean state.

Quoted: For instance, you may want your cache to be varied based on some internal state and/or property of your application. I'll use an example to demonstrate...

Some great tips in here.

Quoted: Web App Follies: Keep Sites Running Smoothly By Avoiding These 10 Common ASP.NET Pitfalls -- MSDN Magazine, July 2006
...
LoadControl and Output Caching
Sessions and Output Caching
Forms Authentication Ticket Lifetime
View State: The Silent Perf Killer
SQL Server Session State: Another Perf Killer
Uncached Roles
...