Featured post
iis 7 - .NET Framework 1.1 on IIS 7 -
i have inherited .net framework 1.1 web site must host iis 7 on windows server 2008. i'm having trouble.
1. installation
i installed .net framework 1.1 following these instructions.
the installation automatically created new application pool "asp.net 1.1". use that.
2. trouble
when launch web site see web.config runtime errors:
the tag contains invalid value 'culture' attribute.
i fix 1 , see:
child nodes not allowed.
i don't want keep playing whack-a-mole game. something must wrong.
3. sure .net 1.1?
i examine automatically created application pool. see it's 1.1.
advanced settings...
basic settings...
this doesn't seem right.
while 1.1 set, it's not option in advanced drop down selectors.
and why in basic box "v1.1" , not ".net framework v1.1.4322"? more consistent.
4. cannot create other .net 1.1 app pools
i cannot select .net framework 1.1 other application pools. it's not option in drop down selectors. what's that?
what now?
- why isn't v1.1 option apppools?
- how can verify application in fact using .net framework 1.1?
- why might these runtime errors?
a quick-fire way find out if application running under 1.1 knock quicky script displays environment version:
<%@ page language="c#" %> <script runat="server"> void page_load(object sender, eventargs e) { response.write(system.environment.version.tostring()); } </script>
or if you're getting yellow screens of death you'll see version number @ bottom of page:
i suspect reason can't select framework v1.1 when adding new application pool or modifying existing 1 1.1 installer doesn't know how add critical piece of metadata or config info iis.
.net 2.0 ships 2008 , .net 4.0 being later product iis7 friendly there better iis integration. or, v1.1 doesn't have essential nugget of metadata iis7's inetmgr needs able add various lists.
the reason can see v1.1 in drop downlist asp.net 1.1 pool basic settings dialogue , not other pools because it's been set , included in list. experimented , changed on newly created asp.net 1.1 pool , set 2.0, saved, re-opened. result v1.1 isn't visible more.
additionally reason it's called v1.1 , not .net framework v1.1.4322 because value being picked managedruntimeversion
attribute in app pool config in applicationhost.config
. reason versions 2.0 , 4.0 show full description there's piece of iis friendly metadata resource string being looked isn't present 1.1.
to set pool use v1.1 @ creation time have manually set managedruntimeversion
attribute using appcmd.exe
:
appcmd add apppool /name:"newpool" /managedruntimeversion:"v1.1"
this explained @ bottom of article linked to.
to change existing pool use 1.1 must use command line appcmd.exe
tool:
appcmd set apppool /apppool.name:"someotherpool" /managedruntimeversion:"v1.1"
interestingly can set managedruntimeversion
old value:
i wish explain away why asp.net 1.1 application pool magically gets created or how installer manages right thing handler mappings (somehow correct preconditions
set, either installer has been updated or iis has kind of trigger 1.1 being installed , fix things).
update:
i contacted bill staples, author of article:
i asked him how 1.1 installer or iis7 manage right thing regarding handler mappings, creating "asp.net 1.1" application pool , on. reply:
"if memory serves, in vista/windows 2008 there application compatibility shim created detect 1.1 installer , app pool creation/handler mapping. however, in windows 7 / windows server 2008 r2, .net framework 1.1 no longer supported , wouldn't surprised if code pulled, though don't know sure."
so mystery solved.
- Get link
- X
- Other Apps
Comments
Post a Comment