Last night was a day I decided to play with some code development. It's not often I get time to sit down and write some DotNetNuke code, so I figured I'd give it a go.
Being a web developer I usually configure my local hosts file with names to go along with my development sites. For example, santry.local, sitswer.local, etc. This way I can bind them to IIS and browse the sites as I'm developing and debugging.
So after a little while of developing, I'm hitting my own personal here at santry.com, and then I get this weird yellow screen of death error. You know, those types that make an ASP.NET developer cringe.
This lasted for a while, other sites were running fine, but my main site at santry.com wasn't. Since I built it on DotNetNuke, I was swearing up the platform all the way. "Damn application with these crazy ambiguous errors!"
Everything I did, I just couldn't figure out why the site wasn't working.
Then I decided to hit the site using my iPhone, and it worked! I went back to my desktop and it wouldn't. So I'm figuring this must have something to do with my user agent type. I instantly switched the user agent using a handy dandy tool in Chrome, but still the same error. I'm really "WTF'ing?!" at that point.
Then all of the sudden, I realize I'm in my development virtual machine. Open the local hosts file, and right there in front of me is the following entry:
Moral of the story, don't use your development machine to browse production websites. And keep to the convention of using "sitename.local" when binding development sites.
Go figure.... =P