Yeah, apparently there were a few bugs in the RC release, so Microsoft has posted a refreshed RC release.  I really, really hate it when they do things like this.  Yes, I’m all for fixing the bugs, but give it a different name already! How about, I don’t know, RC2?!?

Scary, Scary Words From a Smart Man
I have a lot of respect for Joel Spolsky, but this conversation scares the hell out of me.  I have not listened to the podcast yet, but the transcript made me cringe.  He has some good points, but they are crammed in between a lot of really terrible advice.  Yes, I am a huge fan of testing, but his seeming "you don’t really need to test unless you are writing a compiler" attitude is just wrong.  Industry evidence shows that he is wrong.  Personal experience proves that he is wrong.  Until we started mandating very high test coverage here at my day job, we had crap for code.  Every single release we pushed out was buggy as all get out.  The areas that are still the buggiest are typically the areas with the lowest test coverage, such as the WebForms portion of the app.  The areas that are fully tested are typically much more robust and solid.  Yes, they still have bugs, but overall we have far fewer severe bugs.  My take is that if you can’t prove that something works, it doesn’t work.  Bad Joel! BAD!

Form Validation in ASP.NET MVC
I find it really cool how easy it is to apply validation to an ASP.NET MVC application.  Here’s an example of using IDataErrorInfo.  The upside to this approach is that it will work with other APIs that support the IDataErrorInfo interface (which I believe includes WinForms and WPF).