You only get one CLR per process. The 1.1 code runs in the 2.0 CLR,
which supports all of the IL instructions from 1.1 so there are no
fundamental "it can't work" issues. However, it does mean that the 1.1
code will run with the 2.0 versions of the libraries - i.e. if there
are some obscure changes in ArrayList (or some other type being used
by the 1.1 assembly), then there may be subtle behavior differences.
Marc
> I have a question about the internal working of the CLR when it comes
> to a 2.0 (or higher) asp.net app referencing a library written in 1.1.
[quoted text clipped - 3 lines]
> info written about this subject) or does CLR 2.X.X also handle the 1.1
> library?
The 2.0 Runtime can load and run code from 1.1 assemblies and, for the
most part, they /will/ "just work". Those 1.1 classes, of course,m will
in turn call Framework methods that will now be taken from the 2.0
runtime, but there are /very/ few cases where this should cause you any
grief.
The big "Gotcha!", for anyone with a code base big enough that you can't
recompile everything overnight, is that a 1.1 Process *cannot* load
assemblies built against Fx 2.0 or later.
HTH,
Phill W.
Martijn B - 01 Feb 2008 09:05 GMT
On 31 jan, 14:04, "Phill W." <p-.-a-.-w-a-r...@-o-p-e-n-.-a-c-.-u-k>
wrote:
> > I have a question about the internal working of the CLR when it comes
> > to a 2.0 (or higher) asp.net app referencing a library written in 1.1.
[quoted text clipped - 16 lines]
> HTH,
> Phill W.
Thanks All