Re: ASP.Net 1.1 and 2.0 Coexist?

re:
>> You can choose High (Isolated) or Medium (Pooled) from the
>> Application Protection drop-down list on the Home Directory
>> or Virtual Directory property *** in the IIS Manager, in IIS
>> 5.0/5.1.

> Application protection won't have any effect in this scenario.

Are you saying that you can't run ASP.NET 1.1 and
ASP.NET 2.0 apps concurrently under IIS 5.0/5.1 ?

I figured that isolating the processes in 5.0/5.1 would work
the same way that isolating the processes in IIS 6.0 works.

I *know* that you can't run 1.1 and 2.0 apps in the same process in IIS 6.0.

How can you run 1.1 apps and 2.0 apps in different IIS 5.0/5.1
processes if they are not hosted by different dllhost(s) ?

( i.e., by isolating the 1.1 processes from the 2.0 processes. )

re:
> That setting is ignored unless you are serving classic ASP pages as well.

What would *that* have to do with it ?

An IIS application is an IIS application...is an IIS application,
whether it's an ASP application or an ASP.NET application.

You can't run ASP and ASP.NET 1.1, *nor*
ASP.NET 2.0, applications in the same process.

That's why you have to isolate them to be able to run them concurrently.

Can you explain yourself further ?




Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================
"JIMCO Software" <contactus@xxxxxxxxxxxxxxxxx> wrote in message
news:%23sQaDyBzFHA.2076@xxxxxxxxxxxxxxxxxxxxxxx
> Juan T. Llibre wrote:
>>
>> If you're running IIS 5.0/5.1, run your 2.0 apps either in "High
>> Isolation", isolated from each other *and* 1.1 apps, or in "Medium
>> Isolation", with all 2.0 apps pooled in one process.
>>
>> You can choose High (Isolated) or Medium (Pooled) from the
>> Application Protection drop-down list on the Home Directory
>> or Virtual Directory property *** in the IIS Manager, in IIS
>> 5.0/5.1.

> Application protection won't have any effect in this scenario. That setting is ignored
> unless you are serving classic ASP pages as well.
>
> The only way that you can run ASP.NET in the inetinfo process is to turn off the
> processModel via the machine.config.
>
> --
> Jim Cheshire
> JIMCO Software
> http://www.jimcosoftware.com


.

Loading