Duplicate entries in config files
If there are multiple (conflicting) policy statements for the same assembly in a config file, which policy will fusion take?
In .Net v1.0/v1.1, we will take the first policy. The rest policies are practically no-op.
In .Net 2.0, we will preserve the same behavior.
An example of config file with duplicate entries is shown below:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="myAssembly"
publicKeyToken="32ab4ba45e0a69a1"
culture="neutral" />
<bindingRedirect oldVersion="1.0.0.0” newVersion=”2.0.0.0” />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="myAssembly"
publicKeyToken="32ab4ba45e0a69a1"
culture="neutral" />
<bindingRedirect oldVersion=”1.0.0.0” newVersion=”3.0.0.0” />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>