Raj Kaimal

When using forms authentication with slidingExpiration set to true (default), the cookie is updated only when more than half the timeout value has elapsed. As a result of this, you might be logged off sooner than you think.

Matt Hawley wrote a function for creating passwords which made me post this:

Omer blogs about creating color ascii art from bitmap images - very cool!

Reposting here for the benefit of asp.net developers and Google

The databinding expression <%# some expression %> is evaluated in the language of the page (VB, C#, etc.)  This can have a big impact on the current syntax, so be very careful when you are looking at docs for the language you are using.

Jeff blogs about users that post questions without searching.

What drives me nuts is when somebody posts a question and then replies to their own post with only the following:

I saw the following article on CNN: Simple passwords no longer suffice (June 1, 2004) which reminded me of the RNGCryptoServiceProvider class.

Colt blogs about Obfuscating Web Pages using a commercial product.

WebControls generally render the Id attribute as the ClientId value so that they can be unique from a DOM perspective. The Calendar Control does not seem to follow this.

For example, if you have a Calendar Control Calendar1 in an ascx page WebUserControl, instead of rendering the Id as WebUserControl1_Calendar1 on the parent page, it simply renders it as Calendar1.

When developing a custom webcontrol that “looks at” other controls, it becomes impossible to use the getElementById property on the the calendar control as the ID rendered is different from what you are expecting.