Bad Microsoft!

Eating your own dogfood again, Microsoft?

I’m on a page published by Microsoft, the makers of ASP.NET and the creators of the best practices for its use. Notice how they go to all of the trouble of defaulting the customErrors=”On” in the web.config file when you create a new one. Right, so… what did I see smack in the middle of their public facing ‘unamed purpose site’ today? A stack dump. (Note: it’s a heavily edited screencap so as not to give anything away unduly, but enough to show that it really happened.)

Tsk! Tsk!

(All in good humor, of course.)