So I assume that you have already installed .NET framework 1.1 and .NET 1.1 SP1 on the server but if you haven’t then here are the links to download the same. I am sure all of you might be knowing that Windows server 2008 doesn’t have .NET 1.1 pre-installed like the way it was the case with Windows server 2003. And also .NET 1.1 doesn’t have any 64bit version. # Download .NET Fx 1.1 from http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38&displaylang=en
# Download .NET Fx 1.1 SP1 from http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38&displaylang=en If .NET 1.1 is installed on the server then in IIS7 you should see an application pool with the name “ASP.NET 1.1” . Also under the ISAPI and CGI restriction feature of IIS7 you should see ASP.NET 1.1 extension listed though it might not be allowed by default. Now if you go to the application pools tree view option and try to create a new application pool , you will not see .NET 1.1 framework option under the drop down box.There are couple of ways by which you can either configure an existing or a new application pool to run under ASP.NET 1.1 and here are those. Method 1.Open the ApplicationHost.config file located under the C:\windows\system32\inetsrv\config\ folder and just find the application pool name you are looking to run under .NET 1.1. Suppose the Application Pool Name is “TEST”. This is how the “TEST” application pool element should look like under ApplicationHost.config. <add name="Test" enable32BitAppOnWin64="true" managedRuntimeVersion="v1.1" managedPipelineMode="Classic" autoStart="true" />A thing to note here is that application pool configured to run under .NET 1.1 framework will only be allowed to have Classic Pipeline. Following KB article illustrates this. http://support.microsoft.com/kb/949353Method 2.
Read more: Experience is what you get when you don’t get what you want.
# Download .NET Fx 1.1 SP1 from http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38&displaylang=en If .NET 1.1 is installed on the server then in IIS7 you should see an application pool with the name “ASP.NET 1.1” . Also under the ISAPI and CGI restriction feature of IIS7 you should see ASP.NET 1.1 extension listed though it might not be allowed by default. Now if you go to the application pools tree view option and try to create a new application pool , you will not see .NET 1.1 framework option under the drop down box.There are couple of ways by which you can either configure an existing or a new application pool to run under ASP.NET 1.1 and here are those. Method 1.Open the ApplicationHost.config file located under the C:\windows\system32\inetsrv\config\ folder and just find the application pool name you are looking to run under .NET 1.1. Suppose the Application Pool Name is “TEST”. This is how the “TEST” application pool element should look like under ApplicationHost.config. <add name="Test" enable32BitAppOnWin64="true" managedRuntimeVersion="v1.1" managedPipelineMode="Classic" autoStart="true" />A thing to note here is that application pool configured to run under .NET 1.1 framework will only be allowed to have Classic Pipeline. Following KB article illustrates this. http://support.microsoft.com/kb/949353Method 2.
Read more: Experience is what you get when you don’t get what you want.
Posts
0 comments:
Post a Comment