Re: Latest patch parses 1.1 pages with 2.0

If you do have it, please right-click "Web Sites", select "Properties" and
then the "ASP.NET" tab.
Jot down the ASP.NET version the ASP.NET tab reports...and post it.

It reports 1.1. Same as the aspnet_regiis -lk listing I posted.

Question for you : For your "1.1 sites", have you created IIS *web sites* or *ASP.NET applications* ?
It makes a lot of difference which one you've used.

I know. These are IIS web sites.

Now, back to the issues.

You are in luck, one of the sites is malfunctioning again, on one of the
test servers that I can play with. It is worth noting that this is a site
that was definitely registered to 1.1 prior to a reboot on the server.

The site in question is 2034039847.

Now the output of aspnet_regiis -lk in the 1.1 directory is:
W3SVC/ 1.1.4322.0
W3SVC/1370742412/root/ 1.1.4322.0
W3SVC/1453161142/root/ 1.1.4322.0
W3SVC/2034039847/root/ 1.1.4322.0
W3SVC/2080259255/root/ 1.1.4322.0
W3SVC/2116458577/root/ 1.1.4322.0
W3SVC/370149253/root/ 1.1.4322.0
W3SVC/384844167/root/ 1.1.4322.0
W3SVC/891393290/root/ 1.1.4322.0

The output of aspnet_regiis -lk in the 2.0 directory is:
W3SVC/ 1.1.4322.0
W3SVC/1370742412/root/ 1.1.4322.0
W3SVC/1453161142/root/ 1.1.4322.0
W3SVC/2034039847/root/ 1.1.4322.0
W3SVC/2080259255/root/ 1.1.4322.0
W3SVC/2116458577/root/ 1.1.4322.0
W3SVC/370149253/root/ 1.1.4322.0
W3SVC/384844167/root/ 1.1.4322.0
W3SVC/891393290/root/ 1.1.4322.0

(identical)

The properties for the root site in the MMC plugin show the .Net version as
1.1. The properties for the specific site in the MMC plugin show the .Net
version as 1.1.

I think at this point we have established that 1.1 is the registered
framework. Agreed?

I would copy in your identity file however the site is returning the same
configuration error as earlier:
Configuration Error
....
Parser Error Message: The value for the property 'maxRequestLength' is not
valid. The error is: The value must be inside the range 0-2097151.
....
Line 117: <httpRuntime
Line 118: executionTimeout="90"
Line 119: maxRequestLength="500000000"
Line 120: useFullyQualifiedRedirectUrl="false"
Line 121: minFreeThreads="8"
....
Source File: <path>\web.config Line: 119
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832

Just to be clear, I have removed the path in the code above and replaced it
with <path>.

Now I could fix the config file to run happily under 2.0, and then copy your
identity.aspx file in. That doesn't change the fact that there is a serious
bug here. 2.0 is parsing a config file while everything is reporting that 1.1
is the active framework.
.

Relevant Pages

  • RE: .net framework version, visual studio 03
    ... You can use a config file to direct the runtime to use a particular version ... framework using an older version of VB.net, ... I think you only have to switch one reference for each project, ... When compiling the release, I did the switch. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Remoting Help Required
    ... .config file, register it as a well known type and as long as it's in the ... instances of your app out there pointing to a separate instance of that dll. ... > Now I have a request to run multiple versions of the reports on the ...
    (microsoft.public.dotnet.languages.vb)
  • Re: .Net Framework 2.0
    ... standalone application using a Config file works very well and that will ... may be other applications running in the host process so you couldn't just ... override the use of the .NET framework. ... > version of the CLR is loaded to work around the behavioral differences. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: what does this code block do?
    ... - so I'm guessing the config file gets loaded despite the reported ... If the first five chars of the file are not "<?php" ... why does it pass ** dbloader test? ... things) and reports it as ok ...
    (alt.php)
  • RE: App.Config: using doctype and entity blocks
    ... Block Framework, ... Framework for the manipulation of the App.Config is included as part of the ... fuslogvw reports that the XML config file is not formatted correctly. ...
    (microsoft.public.dotnet.general)