One thing I realized (too late) is that I need to be more careful about picking funny terms to describe things. In early 2004 we had made a new build of the CLR 2.0 we were checking into Windows that did not (yet) have a Visual Studio 2005 that worked...

Most errors you run into when using the .NET Framework throw an exception making it easy to figure out what is going on. However there has always been a class of bugs that are very hard to diagnose. My favorite example is getting a P/Invoke declaration...