http://blog.9cbs.net/images/blog_9cbs_net/qq_net/42570/r_asp_regiis.gif
.NET Framework allows multiple versions of the running library to be installed on the same computer. By default, all ASP.NET applications are automatically updated using newly installed .NET Framework versions on a new .NET Framework version that has been installed .NET Framework The only exception is the application that binds the running library version or updated running library version or update. Although later versions of .NET Framework has backward compatibility, you may still need to configure the ASP.NET application accordingly to use some older version.
The script map for the ASP.NET application If multiple versions of .NET Framework are installed on the same computer, these installations contain each associated ASP.NET ISAPI version. ASP.NET applications use ASP.NET ISAPI to determine which version of the .NET Framework that uses .NET Framework. ASP.NET applications can be configured to use any of the installed ASP.NET ISAPIs. To specify the ASP.NET ISAPI version used by the ASP.NET application, register the script map for the application in the Internet Information Service (IIS).
Script Mapping The file extension and HTTP predicates are associated with the appropriate ISAPI to implement scripting processing. For example, if IIS receives a request for a .aspx file, the application's script map indicates that IIS sends the requested file to the appropriate version of ASP.NET ISAPI. Script mapping of each ASP.NET application is usually set in the Internet Information Services Management Console, which can be applied directly to an application or inherited from the parent application. By default, after the .NET Framework is installed, you will automatically update the script mapping of all existing ASP.NET applications on your computer to use the ASP.NET ISAPI version associated with this installation, unless the application uses a higher version. Or incompatible versions.
To make the script mapping of reconfiguration ASP.NET applications, each .NET Framework installation provides an associated ASP.NET IIS Registration Tool (ASPNET_REGIIS.EXE) version. By default, the tool is installed in the following directory:
Administrators can use this tool to re-map the ASP.NET application to the ASP.NET ISAPI version associated with this tool.
Note Because ASPNET_REGIS.EXE is associated with a specific version of .NET Framework, the administrator must use the appropriate version of ASPNET_REGIIS.exe to reconfigure the script mapping for the ASP.NET application. ASPNET_REGIIS.EXE Reconfigures only the ASP.NET application's script map to the ASP.NET ISAPI version associated with this tool. This tool can also be used to display all installed ASP.NET versions, registration associated ASP.NET versions, create a client script directory, and perform other configuration operations.
For more information on script mapping and IIS configuration, see the IIS documentation. For more information on updating script mappings for a ASP.NET application, see the ASP.NET_REGIS.EXE.
ASP.NET Performance Counters have Performance Counters, you can monitor ASP.NET operations by performance console. Each installation of ASP.NET has a performance counter for an ASP.NET for each version of each version, as well as performance counters suitable for all of the installed versions.
Each version of ASP.NET installs a set of different performance counters objects to monitor the ASP.NET system and ASP.NET applications. These objects use "ASP.NET V.X.XXXX.X" and "ASP.NET Apps v.x.xxxxx.x" naming agreements, where v.x.xxxx.x represents the version number and internal version number of ASP.NET. In addition, ASP.NET also has an ASP.NET system and ASP.NET application performance counters applicable to all ASP.NET versions installed. Because these counters are shared for all versions of ASP.NET, they are constantly installing the latest version installed on your computer. If the latest version of ASP.NET is uninstalled, these counters are reanable to associate with the remaining latest version of ASP.NET.
ASP.NET Status Services ASP.NET Status Services is used to manage session status on your computer. All compatible versions of ASP.NET installed on the same computer share the same status service. The status service version used is always installed with the latest version of ASP.NET. This version is registered under ASPNET_STATE. Therefore, when this version of ASP.NET is uninstalled, the latest version remaining on the computer will register and replace it.
ASP.NET SQL Status Server ASP.NET SQL Status Server is used to manage session status in SQL on your computer. All compatible versions of ASP.NET installed on the same computer share the same SQL status server. The SQL status server version used is always installed with the latest version of ASP.NET. When this version of ASP.NET is uninstalled, the latest version remaining on the computer will register and replace it.
ASPNET User Accounts and Filters Install All versions of ASP.NET share the same ASPNET user account (for assist process) and ASPNET_FILTER.DLL (for storing session IDs and requesting session IDs from without cookie session status requests.) ASPNET users Accounts and ASPNET_FILTER.DLL always correspond to the latest version of the installed ASP.NET. When this version of ASP.NET is uninstalled from your computer, the latest version remaining on your computer will register and replace it.
