IIS 7 is positioned exactly between a rock and a hard place. Its bundled in with the more recent MS Server Products (2008+), but sadly will not install on Windows Server 2003. This is the crux of the matter that unfortunately puts IIS 7 out of reach.
Developers want to work with the most recent technologies. This is seldom possible in the world of Windows development in 2010. In a distributed SOA environment a great deal of customers are still using, yup you guessed it – Windows Server 2003.
Lets say you have a web application, and you install this at your customer sites. Assuming you have more than 1 customer, and hopefully more than 10, a problem will quickly come to light. If just one of your customers has Windows Server 2003, your web app needs to be compatible with the version of IIS that ships with Windows Server 2003, yes ladies and gents IIS6. You cannot assume any of the advanced features in IIS7, you have to code for worst case scenario right? You can’t ship a feature if the client’s server infrastructure doesn’t support it.
The situation gets more cynical when you realize that even without customers, you should infact plan for the worst case scenario. There is still a wide client audience running Win 2k3, hence IIS6 becomes your target web server.
Its 2010 and clients still don’t want to upgrade past Windows Server 2003. Can you truly blame them if Win2k8+ provide no real business value and induces additional costs. Linux outshines Windows in this regard, there is no political motivation to bundle in web server versions with OS version.
The longer I ponder on this article, the more I realize that to a great many developer out there, IIS7 hardly even exists.