Forcing a .net 1.1 web application to always use the 1.1 framework

[appdevtech]

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.
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
</startup>
</configuration>

But I noticed that if the application directory is1.0 and check the version
of a web page using Environment.Ver sion.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

[Jc Morin]

Hi,
I know you can configure per web site / virtual directory a specific version
of the .NET framework.

IIS -> Properties of a Web site.

Go in ASP.NET tab. There is a drop down list with all installed version of
the .NET framework on your server.

Hope that help.

--------------------------
Jean-Claude Morin, MCP
Software Developer
2k1Soft/kCentric, Canada
"appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...

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.
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
</startup>
</configuration>

But I noticed that if the application directory is1.0 and check the version of a web page using Environment.Ver sion.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

[Juan T. Llibre]

re:

Go in ASP.NET tab.
That hasn't been functional since .NET 2.0 Beta 1.
For .NET 1.1, it's OK, though.

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"Jc Morin" <mi************ ****@jcmorin.ne t> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. .. Hi,
I know you can configure per web site / virtual directory a specific
version
of the .NET framework.

IIS -> Properties of a Web site.

Go in ASP.NET tab. There is a drop down list with all installed version of
the .NET framework on your server.

Hope that help.
Jean-Claude Morin, MCP "appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...

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.
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
</startup>
</configuration>

But I noticed that if the application directory is1.0 and check the

version

of a web page using Environment.Ver sion.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

[bruce barker]

no. the version of asp.net is controlled by the IIS mappings.

-- bruce (sqlwork.com)

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
| 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.
| <configuratio n>
| <startup>
| <supportedRunti me version="v1.1.4 322"/>
| </startup>
| </configuration>
|
| But I noticed that if the application directory is1.0 and check the
version
| of a web page using Environment.Ver sion.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
|

[Tampa.NET Koder]

You can do this on the command line:

aspnet_regiis.e xe -s W3SVC/1/ROOT/SampleApp1

SampleApp1 ==> Your virtual directory


"appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...

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.
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
</startup>
</configuration>

But I noticed that if the application directory is1.0 and check the
version
of a web page using Environment.Ver sion.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

[Tampa.NET Koder]

** NOTE:

You must be inside the .NET framework version folder that you want to
configure this site for unless it will default to the most recent installed
version. aspnet_regiis.e xe can be found in all of the framework folders. E.g
C:\WINDOWS\Micr osoft.NET\Frame work\v1.1.4322 OR,
C:\WINDOWS\Micr osoft.NET\Frame work\v1.0.3705 OR,
C:\WINDOWS\Micr osoft.NET\Frame work\v<2.0 verision number>
**
"appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...

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.
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
</startup>
</configuration>

But I noticed that if the application directory is1.0 and check the
version
of a web page using Environment.Ver sion.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

[appdevtech]

So what is the <supportedRunti me version="v1.1.4 322"/> used for then, if I
can't use it to force an application to run 1.1?

"bruce barker" wrote:

no. the version of asp.net is controlled by the IIS mappings.

-- bruce (sqlwork.com)

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
| 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.
| <configuratio n>
| <startup>
| <supportedRunti me version="v1.1.4 322"/>
| </startup>
| </configuration>
|
| But I noticed that if the application directory is1.0 and check the
version
| of a web page using Environment.Ver sion.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
|

[Juan T. Llibre]

http://msdn.microsoft.com/library/de...imeElement.asp

It's not used to "force" an application
under a particular runtime.

It *does* indicate which versions
of the runtime are supported.

Targetting multiple versions of the runtime
is perfectly possible with <supportedRunti me version=...>
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
<supportedRunti me version="v1.0.3 705"/>
</startup>
</configuration>
I think you're referring to :
<requiredRuntim e version="v1.1.4 322"/>

That *requires* that the app run under 1.1.4322.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:02******** *************** ***********@mic rosoft.com...

So what is the <supportedRunti me version="v1.1.4 322"/> used for then, if I
can't use it to force an application to run 1.1?

"bruce barker" wrote:

no. the version of asp.net is controlled by the IIS mappings.

-- bruce (sqlwork.com)

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
| 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.
| <configuratio n>
| <startup>
| <supportedRunti me version="v1.1.4 322"/>
| </startup>
| </configuration>
|
| But I noticed that if the application directory is1.0 and check the
version
| of a web page using Environment.Ver sion.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
|

[appdevtech]

Doesn't <requiredRuntim e version="v1.0.3 705"/> only work for 1.0?

http://msdn.microsoft.com/library/de...redRuntime.asp

"Juan T. Llibre" wrote:

http://msdn.microsoft.com/library/de...imeElement.asp

It's not used to "force" an application
under a particular runtime.

It *does* indicate which versions
of the runtime are supported.

Targetting multiple versions of the runtime
is perfectly possible with <supportedRunti me version=...>
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
<supportedRunti me version="v1.0.3 705"/>
</startup>
</configuration>
I think you're referring to :
<requiredRuntim e version="v1.1.4 322"/>

That *requires* that the app run under 1.1.4322.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:02******** *************** ***********@mic rosoft.com...

So what is the <supportedRunti me version="v1.1.4 322"/> used for then, if I
can't use it to force an application to run 1.1?

"bruce barker" wrote:

no. the version of asp.net is controlled by the IIS mappings.

-- bruce (sqlwork.com)

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:A1******** *************** ***********@mic rosoft.com...
| 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.
| <configuratio n>
| <startup>
| <supportedRunti me version="v1.1.4 322"/>
| </startup>
| </configuration>
|
| But I noticed that if the application directory is1.0 and check the
version
| of a web page using Environment.Ver sion.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
|

[Juan T. Llibre]

Yes.

That was a copy-and-mangled-paste typo.

That should have been:

I think you're referring to :
<requiredRuntim e version="v1.0.3 705"/>

That *requires* that the app run under 1.0.3705.
Thanks for noticing!


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:3E******** *************** ***********@mic rosoft.com... Doesn't <requiredRuntim e version="v1.0.3 705"/> only work for 1.0?

http://msdn.microsoft.com/library/de...redRuntime.asp

"Juan T. Llibre" wrote:

http://msdn.microsoft.com/library/de...imeElement.asp

It's not used to "force" an application
under a particular runtime.

It *does* indicate which versions
of the runtime are supported.

Targetting multiple versions of the runtime
is perfectly possible with <supportedRunti me version=...>
<configuratio n>
<startup>
<supportedRunti me version="v1.1.4 322"/>
<supportedRunti me version="v1.0.3 705"/>
</startup>
</configuration>
I think you're referring to :
<requiredRuntim e version="v1.1.4 322"/>

That *requires* that the app run under 1.1.4322.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"appdevtech " <ap********@onl ine.nospam> wrote in message
news:02******** *************** ***********@mic rosoft.com...

> So what is the <supportedRunti me version="v1.1.4 322"/> used for then,
> if I
> can't use it to force an application to run 1.1?
>
> "bruce barker" wrote:

>> no. the version of asp.net is controlled by the IIS mappings.
>>
>> -- bruce (sqlwork.com)
>>
>> "appdevtech " <ap********@onl ine.nospam> wrote in message
>> news:A1******** *************** ***********@mic rosoft.com...
>> | 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.
>> | <configuratio n>
>> | <startup>
>> | <supportedRunti me version="v1.1.4 322"/>
>> | </startup>
>> | </configuration>
>> |
>> | But I noticed that if the application directory is1.0 and check the
>> version
>> | of a web page using Environment.Ver sion.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
>> |
>>
>>
>>