Configuring IIS 6.0 to Use the Correct Version of the .NET Framework
Updated: August 22, 2005
Applies To: Windows Server 2003, Windows Server 2003 with SP1
Before upgrading a Web server that hosts ASP.NET applications, version 1.0 of the .NET Framework is installed on the server and the applications are configured to use that version of the .NET Framework. After upgrade, version 1.1 of the .NET Framework is installed and the applications are configured to use version 1.1 of the .NET Framework. However, version 1.0 of the .NET Framework is still installed, which is referred to as side-by-side support.
Running versions 1.0 and 1.1 of the .NET Framework side-by-side is only supported when IIS is configured to run in IIS 5.0 isolation mode. If you have already configured IIS to run in worker process isolation mode, then you can only use version 1.1 of the .NET Framework. In most cases, ASP.NET applications function correctly with version 1.1 of the .NET Framework. For more information about possible application incompatibilities when upgrading from version 1.0 to version 1.1 of the .NET Framework, see Determining Application Compatibility with the .NET Framework. When your ASP.NET application is incompatible with version 1.1 of the .NET Framework, configure the application to use version 1.0 of the .NET Framework and configure IIS to run in IIS 5.0 isolation mode.
You can configure each ASP.NET application to use a specific version of the .NET Framework by registering a script map in IIS for the application. A script map associates a file name extension and HTTP verb with the appropriate Internet Server API (ISAPI) for script handling. For example, when IIS receives a request for a .aspx file, the script map for the corresponding application directs IIS to forward the requested file to the appropriate version of the ASP.NET ISAPI for processing.
The script map for each ASP.NET application can be applied directly to an application, or inherited from a parent application. However, ASP.NET supports only one version of the .NET Framework for each application pool. For more information about how to configure the script map for an ASP.NET application, see Configure an ASP.NET Application for ASP.NET.