ASP.NET 2.0 (3.0 and 3.5) are easy to install with Windows Vista and Windows 2008 - just install the ASP.NET component located under IIS->Word Wide Web Services->Application Development Features. You can find this set of components in Windows 2008 by clicking Start, and click Server Manager. Expand the left-hand treeview in Server Manager and click Manage Roles, and then Web Server (IIS). In the right-hand pane look for an option that says Add Role Services. If you're on Windows Vista, click Start, click Control Panel, click Programs, and then Windows Features. Look for the following tree of features under Internet Information Services (IIS):
ASP.NET 1.1 is not included in Windows Vista or Windows 2008 and must be downloaded and installed manually. This post shows you how:
Step 1: Install "IIS Metabase Compatibility"
The IIS7 "Metabase compatibility" component is required to successfully install ASP.NET 1.1.
To install it on Windows 2008 Server, click Start, and click Server Manager. Expand the left-hand treeview in Server Manager and click Manage Roles, and then Web Server (IIS). In the right-hand pane look for an option that says Add Role Services. This takes you to wizard where you can install "IIS Metabase Compatibility".
If you're on Windows Vista, click Start, click Control Panel, click Programs, and then Windows Features. Look for Internet Information Services (IIS) and install "IIS Metabase Compatibility".
Step 2: Install the .NET Framework v1.1 and .NET Framework v1.1 SP1
Install Framework v1.1, SP1, and ASP.NET's security update to SP1:
- .NET Framework Version 1.1 Redistributable Package
- .NET Framework Version 1.1 Service Pack 1
- ASP.NET Security Update for .NET Framework 1.1 SP1
When you install .NET Framework Version 1.1, and SP1 for .NET Framework Version 1.1, you'll see the following dialog. Click Run program.
note: If you do not install Framework v1.1 SP1, you may run into Data Execution Prevention errors with messages like "IIS Worker Process has stopped working". This is expected. Installing .NET Framework v1.1 SP1 will fix this.
Step 3: Enable ASP.NET v1.1 ISAPI Extension
Enable ASP.NET v1.1 ISAPI as an allowed ISAPI extension. To do this, open "IIS Manager" administration tool. In the features view, click on the "ISAPI and CGI Restrictions" feature. In the actions pane, click "add"
note: change drive if your system drive is not C:\
Description: ASP.NET v1.1
You can also do by running the following command line:
Step 4: Add IgnoreSection Handler to v1.1 machine.config
ASP.NET v1.1 will throw runtime exceptions out of the box if you have IIS configuration in the web.config files that are read by your ASP.NET v1.1 applications. To make ASP.NET v1.1 ignore IIS configuration sections, open the Framework v1.1 machine.config file (%windir%\Microsoft.NET\Framework\v1.1.4322\config\machine.config) and add the following section entry just above the bottom tag for the <configSections> element:
<section name="system.webServer" type="System.Configuration.IgnoreSectionHandler,
System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
Step 5: Move Site or Application to ASP.NET 1.1 Application Pool
During installation, Framework v1.1 creates an application pool called "ASP.NET 1.1" that is configured to load Framework v1.1 upon startup. To move your site or application into this application pool using IIS Manager, please see our online documentation. You can also do this from the command line by navigating to the %windir%\system32\inetsrv directory and running the following command line:
appcmd set app "Default Web Site/" /applicationPool:"ASP.NET 1.1"
If you would like to create a new application pool that's configured to load Framework v1.1, please see our online documentation for creating an application pool. You can also do this from the command line by navigating to the %windir%\system32\inetsrv directory and running the following command line:
appcmd add apppool /name:"NewPool" /managedRuntimeVersion:"v1.1"