Assembly Unification

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Juan Ignacio Gelos - 17 Nov 2005 17:51 GMT

(Re: .NET Assemblies versions; I wanted to make this a new poat but OE shows
it in the same thread as the original post, so excuse the repost if you see
both as new threads)

Reading the docs (http://msdn2.microsoft.com/en-us/library/db7849ey ) I
see a note that states: "Version 1.0 .NET Framework assemblies are not
unified. The only way to instruct the runtime to use a .NET Framework
assembly that is not version 1.0 is to create a configuration file that
contains the appliesTo attribute in the <assemblyBinding> element.", which I
interpret to mean that assemblies compiled for .NET 1.0 do not get this
treatment. So I'm guessing the referring assembly (the one that has a
reference to an 1.0 assembly) needs to be compiled on 1.1 and up so it can
be unified?

And my main concern: supposing an assembly that has references to 1.0
.NET assemblies is unified to use the 2.0 framework assemblies, would this
hurt performance in any way? I mean runtime performance, AFTER loading,
since I expect there's gonna be a slight performance hit at load time (I
guess
FUSION does the unification).

Regards,
Juan

"Mattias Sjögren" <mattias.dont.want.spam@mvps.org> escribió en el mensaje
news:%23yn0r0s6FHA.2552@TK2MSFTNGP10.phx.gbl...

>>Does the CLR automatically rebind those references to point to the 2.0
>>versions?
>
> Yes. Search for "assembly unification" in the docs for more details.
>
> Mattias

Reply to this Message

vincehe@online.microsoft.com - 17 Nov 2005 18:47 GMT

What is meant is that V1.0 does not support unification. So, if you run a
v1.1 assembly against v1.0, you not only have to provide a config file with
a Startup section and requiredRuntime element, you also need to provide the
binding redirect list that duplicates the effect of unification.
Unification was developed in the V1.1 time frame to avoid the mix and match
of clearly unmatched (having different versions) system assemblies.

So, dependencies of a v1.0 assembly in a V1.1 or V2.0 application, will be
unified to the appropriate Framework assemblies. There is no perf hit even
while loading, because every load goes through the code path that checks the
unification logic. In most cases, you should see a performance gain when
running against v2.0 and I know of no scenarios where you are likely to see
a performance degrade.

Vince

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

> (Re: .NET Assemblies versions; I wanted to make this a new poat but OE
> shows it in the same thread as the original post, so excuse the repost if
[quoted text clipped - 30 lines]
>>
>> Mattias

Reply to this Message

Rate this thread:

Assembly Unification

Free Magazines