Differences between IIS 6.0 and IIS 5.0

We know that Microsoft has re-designed IIS 6.0 to take advantage of Basic Windows Kernel HTTP. sys. This provides built-in response and request caching and queue functions, and can route application process requests directly to the working process to improve reliability and performance.

IIS 6.0 introduces two operation modes for configuring the application environment: Working Process Isolation Mode and IIS 5.0 Isolation Mode. The default isolation mode when installing IIS 6.0 depends on whether you perform a new installation or upgrade.

After IIS 6.0 is completely installed, IIS runs in Working Process Isolation Mode.

After upgrading from a later version of IIS 6.0, the isolation mode is the same as that configured in the earlier version of IIS 6.0.

After upgrading from IIS 5.0 or IIS 4.0, IIS 6.0 runs in IIS 5.0 isolation mode by default to maintain compatibility with existing applications.

IIS 5.0 Isolation Mode

IIS 5.0 Isolation Mode manages application processes in a way similar to process management in IIS 5.0: all in-process applications run in Inetinfo.exe, an out-of-process application runs in a separate DLL host. Some existing applications may not run concurrently or store session states separately from applications. Therefore, running processes in IIS 5.0 Isolation Mode ensures compatibility with most existing applications.

Configure Database Configuration

The configuration database of IIS 6.0 is stored as an XML file instead of binary format in earlier versions. The operation method (Update, rollback, restore, and extension) has changed. There are two important files: MetaBase. xml and MBSchema. xml.

For more information about IIS database configuration, see about database configuration.