Installation of .NET Framework 3.0 RC1 blocks subsequent registration of ASP.NET

Craig McLuckie just compiled documentation that details work around instructions for common .NET Framework 3.0 setup issues. You can find the full document on the WCF Forums titled Common WCF RC1 Installation Issues. The following is a WCF specific issue captured as a separate blog post here for ease of search.

Problem: Installation of .NET Framework 3.0 RC1 blocks subsequent registration of ASP.NET

Source of issue:

There is an installation bug in the .NET Framework 3.0 release that manifests if the .NET Framework 3.0 installer is run on a that has IIS is installed, but does not have ASP.NET registered. On such a system, users will experience difficulty registering ASP.NET.

Symptoms:

When a user runs ‘aspnet_regiis.exe’ after a .NET Framework 3.0 install, the command will execute without generating an error, but the system will not have registered the ASP.NET script maps. ASP.NET pages will be rendered as plain text until the problem is resolved.

Resolution:

You can work around this problem by removing WCF script mappings, re-registering ASP.NET, and then re-registering WCF. Run the following commands from a command console:

1. %windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe –k:W3SVC

2. %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –s W3SVC

3. %windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe –s:W3SVC

Note: This issue will be addressed in future versions of the .NET Framework 3.0.

Mark Gabarra

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at https://www.microsoft.com/info/cpyright.htm