Upgrading from IIS 7.0 to IIS 8.0
Upgrading from IIS 6.0 to IIS 7.0 was a major issue for many organizations. Not only was the operating system being upgraded, but the many changes from IIS 6.0 to IIS 7.0 made programming changes to applications inevitable. With few viable upgrade paths, many organizations chose to upgrade only when a new application version was created. But this is not a problem with IIS 8.0.
There are virtually no changes to IIS 8.0 code from IIS 7.0, only additions. This means that any IIS 7.0 application or website should run directly when deployed into an IIS 8.0 environment, with a few exceptions.
The most notable exception to a clean upgrade is legacy code imported from prior versions of IIS that use various workarounds to run on IIS 7.0. These workarounds will normally work on IIS 8.0 as well, but future upgrades on IIS 8.0 may be in jeopardy. If you have legacy code, a thorough review is in order before upgrading.
The other exception to a direct upgrade path from IIS 7.0 to IIS 8.0 is when the underlying hardware won't support an operating system upgrade. This usually occurs when a 32-bit version for Windows Server 2008 is running on 32-bit hardware. Windows Server 2012 and IIS 8.0 are not compatible with 32-bit hardware. In these cases, a direct operating system upgrade cannot be performed, and a swing, or migration, upgrade is in order.
An in-place upgrade from Windows Server 2008 with IIS 7.0 on compatible hardware is as easy as upgrading the operating ...
Get Professional Microsoft IIS 8 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
