dotnet clr: <inline>

[quoted text, click to view]

Yes - if two parts of an application have been built against different
versions of the same assembly it will load two versions (assuming no version
redirection)

[quoted text, click to view]

Same as 1) if loaded from a codebase hint - if by probing no as it will only
find the first on the probing path and one of the loads will fail due to a
version mismatch.

[quoted text, click to view]

No, for non-strong named assemblies version information is ignored

[quoted text, click to view]

No, for non-strong named assemblies version information is ignored

[quoted text, click to view]

As far as the runtime is concerned any difference in assembly name is a
different assembly. Therefore, types from one version of an assembly cannot
be used in place of those in a differenct version of an assembly.

[quoted text, click to view]

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

I have a question regarding assembly loading.Basically I am asking whether
or not the
assembly loader can load multiple versions of the same assembly if:

1. The assemblies are strongly named and lies in the GAC

2. The assemblies are strongly named and lies outside the GAC

3. The assemblies are not signed and loaded using the Load method with a
partial qualified reference(incomplete four-part name).

4. The assemblies are not signed and loaded using the Load method with a
fully qualified reference(complete four-part name).

If it can load multiple versions of the same assembly how does the CLR
differ between types in one version of the assembly
and types in another version? Also this question applies to both statically
bound assemblies as dynamically bound assemblies.

regards
Kjetil Kristoffer Solberg