Unification Policy- February 15, 2004 The CLR&8217;s strict versioning binding policy for strongly-named assemblies was the first step towards alleviating the &8220;DLL-hell&8221; problems of the past. Whenever you link to a strongly-named assembly, the exact identity of the referenced assembly is recorded in your assembly&8217;s metadata, and Fusion will bind to exactly the same version at runtime (binding policy aside). This ensures that the components the developer tested at design-time is exactly what the user will use a...http://blogs.msdn.com/alanshi/archive/2004/02/15/73244.aspx |