Removing HTML errors in VS2003

We have a lot of custom tags in our applications that are pre-built, and we use them every time. Unfortunately, VS 2003 doesn't like them and we get oddles of HTML validation errors. Not a huge deal but definitely annoying when compiling.

Turns out this can be turned off, obviously not always a good thing but in my case I never look at them anyways so I may as well get them out of there.

The below dialog can be found under "Tools", "Options".

More details (and more elegantly put) below. Also nice to see that the errors have been changed to warnings in VS2008 (post Beta 2 release).

http://weblogs.asp.net/scottgu/archive/2007/09/18/vs-2008-support-to-treat-html-css-and-jscript-validation-issues-as-warnings-instead-of-errors.aspx

http://weblogs.asp.net/scottgu/archive/2005/11/23/431350.aspx

Practical Functional Programming

I don't want my blog to become a "list of links", but the below 4 articles are well worth reading. Definitely a different way to program/code.

http://www.atrevido.net/blog/2007/08/12/Practical+Functional+C+Part+I.aspx
http://www.atrevido.net/blog/2007/08/13/Practical+Functional+C+Part+II.aspx
http://www.atrevido.net/blog/2007/08/16/Practical+Functional+C+Part+III+Loops+Are+Evil.aspx
http://www.atrevido.net/blog/2007/08/29/Practical+Functional+C+Part+IV+Think+In+ResultSets.aspx

My only concern is that C#/VB.Net is going to become a very hard language for newbie's to easily pick up. Sure, they don't have to learn lambda expressions or LINQ, but the difference between a "for" loop and LINQ is pretty significant from a learning point of view. That being said, less code = less bugs so they probably should jump in and learn the useful stuff first.