Problem running ASP.NET 1.1 and 2.0 apps on the same server...

[Kevin S. Goff]

I'm coming into a situation where a company has both 1.1 and 2.0
ASP.NET apps on the same server.

Each application has been configured (using IIS) for the appropriate
framework (on that last ASP.NET tab in configuration management).

Here's the problem. When we configure a 2.0 app, it "breaks" the 1.1
apps. By "break", I mean that when we run them in a browser, we get an
error that the server can't locate the app.

We have to go "re-configure" the 1.1 app by (as crazy as this sounds)
pulling up the 1.1 app, switching the pulldown to 2.0 and then
immediately setting it back to 1.1 to "reconfigure" it for 1.1.

But then it breaks the 2.0 app....and to get the 2.0 app to run, we
have to go into IIS and reconfigure it for 1.1 and then back to 2.0.

We also have a 2nd problem - which may or may not be related. When we
try to build the 2.0 solution on our network (web server) drive, we
get a VS2005 build error about aspnetPermissions. I thought it might
have to do with medium trust levels, but even if we temporarily set
the trust levels to full trust, it doesn't solve the build error.

Anyway, does anyone have any clues or thoughts?

Thanks,
Kevin

 

[Christopher Reed]

At what level in IIS are you configuring ASP.NET? On my Windows XP laptop,
I have my Default Web Site configured for 1.1, but I have a subweb
configured for 2.0. I have not any problem 1.1 and 2.0 apps working
together.

 

[Eliyahu Goldin]

Kevin,

As Christopher mentioned, you should be able to set the Asp.Net version for
each app separately. Apart of this, if you are running IIS 6, you should
place 1.1 and 2.0 applications into different applications pools.

Eliyahu