 | With so many cool new capabilities in IIS7, and even more new features coming out all the time, it's no wonder you want to move to IIS7. But you work for The Man, and everyone knows The Man wants ROI. He can't just let you go willy-nilly and adopt every cool new technology that hits the street. After all, He has a business to run. And that business currently runs on IIS 6. And he's paid you a lot of money (ok, not that much) to write the code, test the apps, deploy the servers, and keep those HTML pumping machines up and running 24x7x365. And things are running well, right? When was the last time you had to worry about metabase corruption? Or been forced to run IISRESET? Or been paged in the middle of the night with some glorious server 500 error and (of course) the developer who wrote the code is no where to be found?
|  |
