Is it normal that my old projects start running under ASP.NET 2.0 automatically?

Some of them are broken now, and I have to change them back to ASP.NET 1.1 manually in IIS.

Jos

Hi Jos,

Last I heard, the Beta version of v2.0 was not supported along side of v1.1. It is advised that you use a separate machine for Beta.

Hi Jos,

FYI: view post 631622

Colt

Hi Colt, Can you provide details of the issues you are seeing with your v1.1 projects when trying to run on v2.0 - the following page has details of approved breaking changes from v1.1 to v2.0.

Thanks,
Kashif

Wasn't the dotNET versioning system (with strong names) supposed to put an end to this "dll hell" forever?

Apparently, the problem remains...

Jos

Jos,

Yes, in Beta 1, if you install v2.0, all your apps in IIS will be upgraded to v2.0, and you have to manually run "aspnet_regiis -s" on those apps that you want to keep as v1.1.

We're looking to make this better - to install the new version without upgrading existing websites to v2.0.

One known area that is "broken" when upgrading to v2.0 is debugging existing apps using VS 7.1, because you can't debug v2.0 apps with VS 7.1 (you have to use VS 8.0). Did you have something else that was broken, that did not involve debugging?