Running many .net versions on a machine

I am interested in various versions of .net. We have an environment in which we developed applications in various versions (1.1 and 2.0). Now I'm trying to get "forward" for development in version 3.5. The biggest problem is whether these versions will play well together with a single IIS installation. Another caveat is that I am developing Windows XP with Visual Studio 2005 and IIS 5.0. Applications will run on a Windows 2003 server and using IIS 6.0. From what I saw, it looks like each IIS virtual directory can install its own version of .net. Isn’t this enough to ensure that diverse applications using diverse versions of .Net do not influence each other?

I will answer any answers that I can get, but it would be extremely useful if you could refer to your answer with some documentation directly from Microsoft (my company pays a lot of attention to “direct listening through the clock”)). However, I will really accept any answers here. Story from the ditches are also welcome.

Thanks!

+3
source share
4 answers

The biggest problem that you will encounter with v.1.1 and v.2.0 hosting applications is that you will need two application pools.

One for websites v.1.1, and the other for websites v.2.0 and higher.

.Net 3.0 3.5 - .Net 2.0, Runtime. - - . - .Net 2.0 .NET 3.5 SP1 -.

IIS 6.0 , IIS 5.0 .

Win 2k3 Vista (IIS 7.0).

+6

, - Visual Studio 2005 XP (IIS 5.0). , .NET 3.5 Visual Studio 2005. Visual Studio 2008.

+1

Windows 2003 . , , , .

BTW: - , . , (, ..) ..

0

.

0