In addition, Jeff Prosise has some 130 pages of whitepaper info on all this stuff here.
Up until now, there was some spotty information on blogs and gotdotnet.com sample submissions, but this is the first time I've seen everything nicely packaged up "under one roof".
I particularly enjoyed writing custom SQLite Membership and Role Providers, as well as some current work I'm doing on a searchable Profile Provider (e.g., give me all the members who have X, Y and Z). So this is a welcome addition.
This is one part of ASP.NET 2.0 that they got right IMHO.
For reference purposes, here is a link to Scott's original blog post:
Safe Method Versions
Do you ever have some coding issue or requirement that kinda annoys you but you keep going along doing it anyway? I think it would be nice if somebody assembled all this little boogers and put together some sort of utility library for it. I'd sure use it.
I'm talking about things like checking for null values on the QueryString before attempting to use a key. The helper method for that one might be something like this:
public static string SafeGetQueryString(string key)
HttpContext ctx = HttpContext.Current;
if(ctx.Request.QueryString["key"}==null) return String.Empty;
-- any required null or other testing would be performed automatically in the method body. I've seen developers make methods like "SafeParseInt" and "SafeIsMACAddress"... Of course in VB.NET a lot of this stuff is done for you under the hood; that's why there is so much room for abuse. Just leave Option Strict and Option Explicit set to "Off" and "code away, Mamma!". Looky here! Everything's an Object anyway, what the hayle do we need to declare and type 'em fer?
Are you up for this, man? Hi, it's [URGENT]. Please send me the answer right away!