Connect Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, 26 July 2012

How to install ASP.NET 1.1 with IIS7 on Windows 2008

Posted on 12:22 by Unknown

Overview

You can use the Web Platform Installer (Web PI) to easily install IIS, and applications that run on IIS. The Web PI is a free, lightweight tool that lets you install IIS and related technologies such as ASP.NET, SQL Server Express, Visual Web Developer, other popular Web applications, and more. Because the Web PI references and links to the latest versions of available Web Platform offerings, with just a few simple clicks you can download and install any new tools or updates.
You can also install ASP.NET 2.0 (3.0 and 3.5) using the Windows Vista and Windows 2008 user interface - 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"
Extension: C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
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:
%windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -enable

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" />
</configSections>


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. 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.  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"



Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • How to schedule a PHP script in task scheduler
    Quiet often there is a need to execute/run  php  script on some time interval at server side. And that php scripts should run automatically ...
  • HTTP Error 403.19 – Forbidden The configured user for this application pool does not have sufficient privileges to run CGI applications.
    If you get the error “HTTP Error 403.19 – Forbidden The configured user for this application pool does not have sufficient privileges to...
  • Roles and Features showing an error HRESULT: 0x800F0818 in Server Manager of windows server 2008 R2
    When you open Server Manager both Roles and Features display Error and you are unable to add any role or features. When you select the det...
  • Error - "Failed to retrieve data for this request (Microsoft.SqlServer.Management.sdk.sfc)"
    ErrError    - In Microsoft SQL Management Studio 2008, you receive the following error message when you try to expand the Databases:      ...
  • How to configure IIS 7 to redirect non-www domain to www domain?
    One of few legacy leftovers that was never dropped over the years is the common use of www domain prefix. It is not a problem per se for us...
  • Back up all MS SQL databases at once
    This article will discuss how to backup all MS SQL databases with one script. A separate file will be created for each database. Log into ...
  • The media family on device is incorrectly formed. SQL Server cannot process this media family Error: 3241
    When you try to restore a backup of the database you get the following error: The media family on device ” is incorrectly formed. SQL Server...
  • How to check Malware injection in Code
    To check Malware injection in your script/Code you can use a Web based Google Tool called “Webmasters Tools” You can find it here Google We...
  • An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
    If you are facing the following error while accessing the website: Error Summary HTTP Error 500.24 - Internal Server Error An ASP.NET settin...
  • Stopping Unneeded Services In Windows Server 2008
    By  default Windows 2008 starts with a number of services that actually do not need to be running. Many of these services can impact perfo...

Categories

  • booting Process
  • linux
  • redhat

Blog Archive

  • ►  2013 (68)
    • ►  July (1)
    • ►  May (2)
    • ►  April (11)
    • ►  March (54)
  • ▼  2012 (44)
    • ►  September (20)
    • ►  August (1)
    • ▼  July (4)
      • How to install ASP.NET 1.1 with IIS7 on Windows 2008
      • Translate .htaccess Content To IIS Web.config
      • Using the Microsoft Web Platform
      • Importing Apache mod_rewrite Rules
    • ►  June (12)
    • ►  May (2)
    • ►  March (4)
    • ►  February (1)
  • ►  2011 (1)
    • ►  February (1)
  • ►  2009 (9)
    • ►  September (3)
    • ►  August (2)
    • ►  June (1)
    • ►  May (2)
    • ►  March (1)
Powered by Blogger.

About Me

Unknown
View my complete profile