G
Guest
A little background…
We have multiple web servers in a farm and are starting to upgrade some
applications to 1.1 by re-compiling in VS2003.
One of the things out of our direct control is the framework version on the
application directory. I'm worried that in the future some directories could
be reverted back to 1.0 on all or some of the servers.
I was hoping I could force the applications I choice to always use 1.1 by
putting this in the web.config, hence overriding what the virtual/application
is configured to use.
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
</startup>
</configuration>
But I noticed that if the application directory is1.0 and check the version
of a web page using Environment.Version.ToString(), it still says the
application is running 1.0 even though I specified v1.1.4322 in the
web.config.
So besides changing the application directory are there any other ways to
verify/force the applications to use the 1.1 framework?
Thanks
We have multiple web servers in a farm and are starting to upgrade some
applications to 1.1 by re-compiling in VS2003.
One of the things out of our direct control is the framework version on the
application directory. I'm worried that in the future some directories could
be reverted back to 1.0 on all or some of the servers.
I was hoping I could force the applications I choice to always use 1.1 by
putting this in the web.config, hence overriding what the virtual/application
is configured to use.
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
</startup>
</configuration>
But I noticed that if the application directory is1.0 and check the version
of a web page using Environment.Version.ToString(), it still says the
application is running 1.0 even though I specified v1.1.4322 in the
web.config.
So besides changing the application directory are there any other ways to
verify/force the applications to use the 1.1 framework?
Thanks