Quick Hits
Brad Wilson has been writing about xUnit.NET, most recently about support for crosscutting concerns. I always liked the support for DB Rollback in MBUnit, and I've tried to write the equivalent of [AssumeIdentity] for NUnit, and it was really a pain.
I've been reading a lot about the future of Microsoft Office, most recently from Dare Obasanjo. I just keep thinking about Joel's Bloatware and the 80/20 Myth, where he basically asserts that Office is successful because in an application that big, 80% functionality doesn't satisfy enough users to be successful. I'm not sure about that conclusion. Office had enough other reasons: document lockin, most notably. I remember in 1997, Word 97 was like a virus: one employee would distribute documents in the new format, and everyone else was forced to upgrade in order to read them.
I ran into Adam Tibi's Multiple Fields Validator while searching for a solution where I needed to validate a group of text boxes where at least one text box had to have some text that matched a given regex. It's a good start for that solution, but it definitely has a bit of an impedance mismatch with the framework. Validation is definitely written with the assumption that a validator applies to a single control. I was intrigued by the ValidationGroup property of BaseValidator, but it turns out to simply allow you to get around ASP.NET's prohibition on multiple <form> elements - you can use ValidationGroup to have separate submit buttons with distinct validation requirements.