Re: Forcing ASP.NET 1.1 isn't working

..NET is backward compatible, not forward compatible. So, code written and compiled on 2.0 will not run on 1.x, just as you see.


"slolife" <slolife@xxxxxxxxx> wrote in message news:1193202386.931708.112010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have an W2k3IIS server with .NET 1.1 and 2.0 installed. I have a
website, which I'd like to run as 1.1. So I go to that website/app's
properties, and on the ASP.NET tab, I select 1.1.

I have a test page that triggers an event validation (which is a
feature introduced in 2.0). I hit that test page and the error is
generated. So apparently, the site (or, what it really looks like, is
just the page) is still running in 2.0. So I add the following


The site DOES NOT run in 2.0. It runs in 1.1, so your code developed on 2.0 causes error: 1.1 runtime does not know 2.0 code.
You can do the opposite: developing app with 1.x, and run in with either 1,x or 2.0 runtime.


startup tag to the web.config in the <configuration> tag:

<configuration>
<startup>
<requiredRuntime version="v1.1.4322"/>
<supportedRuntime version="v1.1.4322"/>
</startup>
...
</configuration>

The page still causes the event validation error (meaning, still
running as .NET 2.0).

So what am I doing wrong here? What do I need to do to get the site/
page to run as 1.1?

NOTE: One of the ways I know the page is running 2.0 is that I can add
the attribute enableEventValidation into the @Page directive and the
page compiler doesn't choke.


.

Relevant Pages