Windows Server 2012 with ASP.net 1.1?

Question

Is it possible to install ASP.net 1.1 on Windows Server 2012? Have some legacy applications that would be too time consuming/expensive to port at the moment.

I was able to go through a convoluted process on Windows Server 2008 where I assembled an installer package. Not sure if the same thing would work on Server 2012.

Anybody have experience getting this working?

Answer 1

It is possible to get ASP.NET 1.1 working..

I've just got a site that depends on ASP.NET 1.1 to run on Server 2012 R2 (so that's IIS 8.5), using the following steps:

• Install "IIS Metabase Compatibility"
• Install the .NET Framework V1.1 and .NET Framework V1.1 SP1
• Enable ASP.NET V1.1 ISAPI Extension - Allow ASP.NET 1.1
• Add IgnoreSection handler To V1.1 Machine.config
• Updated site to use ASP.NET 1.1 Application Pool

http://www.iis.net/learn/install/installing-iis-7/how-to-install-aspnet-11-with-iis-on-vista-and-windows-2008

• Removed the double slash from ISAPI filters.

https://community.rackspace.com/products/f/25/p/820/4868.aspx#4868

• Copied the machine.config file into the 64 bit framework folder for .net 1.1.

  (although i'm running the app pool in 32 bit mode so perhaps this doesn't apply)

https://community.rackspace.com/products/f/25/t/820

• Add the following 'handler' overrides to the sites web.config.

(note system.webServer element may already exist)

<system.webServer>
    <handlers>
        <add name="ASPNET-ISAPI-1.1-WebServiceHandlerFactory" path="*.asmx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv1.1,bitness32" />
        <add name="ASPNET-ISAPI-1.1-SimpleHandlerFactory" path="*.ashx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv1.1,bitness32" />
        <add name="ASPNET-ISAPI-1.1-HttpRemotingHandlerFactory-soap" path="*.soap" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv1.1,bitness32" />
        <add name="ASPNET-ISAPI-1.1-PageHandlerFactory" path="*.aspx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv1.1,bitness32" />
        <add name="ASPNET-ISAPI-1.1-HttpRemotingHandlerFactory-rem" path="*.rem" verb="*" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll" resourceType="Unspecified" preCondition="classicMode,runtimeVersionv1.1,bitness32" />
        <remove name="ASPNET-ISAPI-1.1-AXD" />
        <add name="ASPNET-ISAPI-1.1-AXD" path="*.axd" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv1.1,bitness32" />
    </handlers>
</system.webServer>

http://skills2earn.blogspot.co.uk/2015/01/run-aspnet-website-with-net-framework.html

It was this last step that had me guessing for a long time.