Memo to me:  If VS.NET doesn't want to think IIS is installed when it is, check that nothing is blocking port 80.

 Yeah, so I got a new laptop recently...Dell Latitude D600.  Let me just say, I hate rebuilding my dev machine.  I get it exactly how I want it over a period of a couple of months, and then bam! I'm starting over.  So be it.

So I installed VS.Net and all my other software, including my Top 10 Non-MS Programs, and then go to get some work done.  Open a web project, IIS gags.  Tells me I don't have the framework, or IIS, or some nonsense.  I reinstall all that.  Still no go.  I don't understand, it was working 5 minutes ago...what the hell?

Close down some stuff about to restart, then try to open it again.  Everything fine.  Mmmkay...

Work all day.  All is well.  Take laptop home (without shutting down, mind you) all is well.  Get some more work done.

Come back to office in morning.  Boot up.  No work.  WTF?!?!?!?!?!

Start to go nuts.  Looking up KB articles.  Reinstalling VS.Net.  Nothing is working.  Why does this new laptop hate me?

Searching and searching.  Google seems to be letting me down.  Microsoft seems to be letting me down.  Can't figure it out.  Finally, on like page 20 of search results, I find a blog entry (sorry to whomever, I didn't bookmark so now I forget it) about the same thing.  This guy says run netstat, that Skype is blocking port 80.  I run netstat.  Skype has port 80 in BLOCK_WAIT.  OMG.  Close Skype.  All is well again.

Good news is Skype has a setting you can change to make it leave port 80 alone.  I could have screamed.

Now playing: Hoobastank - The Reason