Tuesday, November 20, 2007 3:46 PMHi, I just upgraded to .NET 3.5, but in my web browser, ASP.NET still reports this:
Is that correct? I don't get the different between .NET and ASP.NET. Aren't they the same thing?
Thanks for any help.
Tuesday, November 20, 2007 6:20 PM
The Framework 3.5 uses the 2.0 CLR, so it may report the misleading number. I'm not sure what its meant to say, though. If someone can post what their correctly working IIS/ASP setup looks like, that'd be great, else, try this from the readme.txt
2.1.4. .NET Framework 3.5 installation might not configure IIS correctly on Windows XP or Windows Server 2003
Installation of .NET Framework 3.5 will not configure IIS correctly on Windows XP or Windows Server 2003 if IIS is already installed and the IIS Admin Service is disabled.
To resolve this issue:
Do the following things after you install .NET Framework 3.5.
1. On the Start menu, click Run.
2. Type "cmd" and then press ENTER.
3. Type "sc config iisadmin start= auto" and then press ENTER.
1. On the Start menu, click Run.
2. Type "services.msc" and then press ENTER.
3. Select the IIS Admin Service from the list. If the Startup Type is Disabled, right-click IIS Admin Service and then click Properties. Change Startup Type to Automatic.
4. In %WINDIR%\Microsoft.NET\Framework\v3.5\, run WFServicesReg.exe /c. (On 64-bit computers, the path is %WINDIR%\Microsoft.NET\Framework64\v3.5\.)
Wednesday, November 21, 2007 5:42 AMModerator
System.Web.Dll is indeed version 2.0.50727.1433 for NETFX 3.5 RTM.
Wednesday, November 21, 2007 9:10 AM
I tried this solution but this error message appear:
Warning: CScriptMapsComponent::Install Cannot set application extensions because the ISAPI Filter path 'C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll' for .aspx doesnot match the expected path 'c:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll'.
(with a french Windows Server 2003 STD)
Tuesday, January 08, 2008 11:17 AM
@DtTissod: I resolved this by re-registering asp.net 2 using aspnet_regiis.exe -i, but then second problem occurred: WFServicesReg.exe /c /v shows errors like these:
CFxInstaller:etupExtensions extensionElement.AddToConfigFile failed. value=System.ServiceModel.Configuration.PersistenceProviderElement, System.WorkflowServices, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Error code: 0x80004005.
This server for testing purposes has .NET 1.1, 2, 3 and 3.5 installed. Any help with the error above will be appreciated.
Tuesday, January 08, 2008 5:52 PM
Please note that WFServicesReg.exe installs scriptmaps only if ASP.NET 2.0 is enabled for the root Websites. The error message says that 1.1 is enabled for root websites and hence WFServicesreg.exe cannot install 3.5 scriptmaps. 3.5 scriptmaps works with ASP.NET 2.0. So in order to get rid of this error. Go to inetmgr, go to WebSites root node. right click properties, In ASP.NET tab select ASP.NET 2.0. Click ok. Verify that .aspx value has 2.0 in properties dialog of root websites node-> home directory tab -> configuration. Then run WFServicesReg.exe /c.
Tuesday, January 08, 2008 5:58 PM
"I just upgraded to .NET 3.5, but in my web browser, ASP.NET still reports this:
This is correct. ASP.NET uses CLR 2.0 and it should show 2.0.50727.1433 in web browser. .NET 3.0 just came with additional features like WCF, WF which inturn uses CLR 2.0 So the run time doesnt change. 3.5 came with some additional features for 3.0 and also SP1s for 2.0 and 3.0. So after 3.5 installation the CLR is 2.0 SP1. hence should show 2.0 in webbrowser.
Hope this helps.
Wednesday, April 02, 2008 5:01 PM
This blog entry explains the whole lot to everybody as to why .NET Framework v3.5 doesn't appear on the IIS's ASP.NET properties tab.
Friday, March 13, 2009 7:04 PMIf it helps, one thing I noticed was that IIS was showing the 1.4 version as the default version
if you looked at websites - aspn.net tab in IIS admin.
It was locked (err... unselectable) so I could not select it.
What I did was go under the v2.0.50727 .net folder and ran aspnet_regiis -i.
(I had 1.0, 1.1, 2.0,3.0,3.5 install folders)
These re-reg'd 2.0 and it then showed up in the IIS site .net version.
I then ran the wfservicesreg.exe -i from the 3.5 folder and it ran and
the error "Cannot set application extensions because the ISAPI filter path blahblahblah\v1.1.4322\aspnet_isappi.dll for .aspx does not match the expected path blahblahblah\v2.0.50727\aspnet_isapi.dll...blahblahblah
I was also getting an IIS admin error on iisreset which also went away.. :) Oh, happy days..., but I also
removed NNTP, so that may have fixed the iisadmin error.. dunno..
I also made sure to do an iisreset to make sure all was starting reloaded.
So what I am thinking probably happened is 2.0 did not register correctly as the global default .net dll.
I do remember setting each individual site to 2.0, which should have actually inherited the sections
automagically. It possibly does this so that you make sure the new version of .net works with your
existing site code.
Just a thought.. hope it helps somebody.. seemed to work for me. :)
- Proposed As Answer by Jochen.SL Friday, March 19, 2010 2:27 PM