ASP.Net 1.1 and 2.0 Coexist?

[Guest]

Hi,

I am wondering can I run asp.net 1.1 web apps and asp.net 2.0 web apps on
the same box? If possible how does the web server realize what framework to
use when calling up a particular web app? Is there any settings that I have
to be aware of to make sure one doesn't step on the other?

Also is it possible on a dev box to have Sql server 2000 and Sql server 2005
running on the same box?

Thanks,

JJ

 

[Juan T. Llibre]

re:

I am wondering can I run asp.net 1.1 web apps
and asp.net 2.0 web apps on the same box?

No problem at all.

Just make sure they are running isolated from each other.

1.1 and 2.0 apps must run in different processes.

If you're running IIS 6.0, create a new Application Pool for your 2.0 apps.
Use the IIS Manager, and scroll down to "Application Pools".

You can assign the App to the Application Pool you created in the
Virtual Directory tab of the website's properties in the IIS Manager.

You can create as many App Pools as you want, but be aware that
each Application Pool means at least another 30-40MB ram minimum.

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 sheet in the IIS Manager, in IIS 5.0/5.1.

re:

If possible how does the web server realize what framework to
use when calling up a particular web app?

By assigning it to the proper .Net Framework version in the
ASP.NET tab in the website's "properties" in the IIS Manager.

re;

Is there any settings that I have to be aware
of to make sure one doesn't step on the other?

What I explain in this post is all you need to do.

re:

Also is it possible on a dev box to have Sql server 2000
and Sql server 2005 running on the same box?

I know that SQL Server 2000 and SQL Server Express 2005 can coexist.
I don't know whether SQL Server 2000 and SQL Server 2005 can coexist.

You might want to ask that question in the SQL Server newsgroups.

 

[JIMCO Software]

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 sheet 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

FrontPage add-ins for FrontPage 2000 - 2003

 

[Juan T. Llibre]

re:

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 ?

 

[JIMCO Software]

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.

You will automatically get one aspnet_wp process for the 1.x app and one for
the 2.0 app. The Application Protection setting is for legacy applications
that run in either a dllhost process or the inetinfo process. ASP.NET
applications have never been affected by that setting.

A classic ASP application is absolutely not the same as an ASP.NET
application. Classic ASP application either run in inetinfo (Low
protection), a shared dllhost process (Medium), or a separate dllhost
process (High). ASP.NET is isolated via the worker process. The
architecture is not the same at all.

If you don't believe me, give it a try! Run an app on IIS 5 under ASP.NET
1.x and another app under 2.0. Check the aspnet_wp process in the process
list. Then change the Application Protection settings for each and see if
there's any difference. There won't be.

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

FrontPage add-ins for FrontPage 2000 - 2003

 

[Juan T. Llibre]

I'll be a horse's *ss.

I wasn't about to wipe a partition and install W2K/IIS 5,
so I did the next best thing in a second dev box I have :

I ran IIS 6 in IIS 5 isolation mode and, you're right, changing the isolation
mode doesn't affect the concurrent running of 1.1 apps and 2.0 apps,
which is diametrically opposed to what the behavior of IIS 6 is, in which
if you don't isolate 1.1 and 2.0 apps in different Application Pools,
the response will be the error message "The Application is Unavailable".

Thanks for pointing this out to me.
( I need more more boxes to run older OS's... )

 

[JIMCO Software]

I'll be a horse's *ss.

I wasn't about to wipe a partition and install W2K/IIS 5,
so I did the next best thing in a second dev box I have :

I ran IIS 6 in IIS 5 isolation mode and, you're right, changing the
isolation mode doesn't affect the concurrent running of 1.1 apps and
2.0 apps, which is diametrically opposed to what the behavior of IIS 6 is,
in
which if you don't isolate 1.1 and 2.0 apps in different Application
Pools,
the response will be the error message "The Application is
Unavailable".
Thanks for pointing this out to me.
( I need more more boxes to run older OS's... )

No problem. Yeah, in IIS 6, you have to keep your app pools all 1.x or all
2.0. Mixing isn't allowed. Make sense since each application pool is akin
to a separate w3wp process.

--
Jim Cheshire
JIMCO Software
http://www.jimcosoftware.com

FrontPage add-ins for FrontPage 2000 - 2003

 

[valalves]

ASP .Net 1.1 and 2.0 on IIS 5.0

Hey Guys,

I was reading the thread and this seems to have answered my question, but since this is kinda new to me, and I'm far from being a developer, I would like to confirm. What I take from this is that changing the isolation
mode doesn't affect the concurrent running of 1.1 apps and 2.0 apps. In this case, what would be the issues with running both versions on the same IIS 5.0 box?