Work Rant

Okay, today I'm going to rant about Windows 2003 and Microsoft Visual Interdev. Please feel free not to read today.

I copied my new application onto a Microsoft Windows 2003 webserver that we have up and running. It didn't work right away so I had to go investigate as to why. Seems as though W3k3 wasn't processing a Server Side Include (SSI.) A little bit of research ... AHH W2k3 ships locked down by default, SSIs aren't processed. No biggie, I turn it on, still doesn't work. AN HOUR I spent searching googol to figure out what was going on. Finally figured it out, and it was nothing with the setup, it was setup fine. See, when VI copies a web application to a new server, it SOMETIMES renames default.asp to default.htm. WELL, for security reasons, .htm files aren't processed as scripts, and they shouldn't be. So the webserver didn't know I had an include file because it was just happy to serve up the .htm file with no problems.

Okay, I knew that was going to be a rant that no one was going to care about.

Ummm, well ... the Phillies won yesterday. Go Phils. Yeah, that is all.