c# – 并排装配加载问题

Assembly.Load("A,Version=1.0.0.0,Culture=neutral,PublicKeyToken=null");
Assembly.Load("B,PublicKeyToken=null");

目录结构是：

所以预期的载荷如下：

TheApp.exe -> A.dll -> C.dll (version 2.0.0.0)
           -> B.dll -> C.dll (version 1.0.0.0)

请注意C.dll已签名,因此两个版本应并排加载.

为确保应用程序从正确的位置加载程序集,我将以下内容添加到应用程序配置文件中：

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="B;A" />
    </assemblyBinding>
  </runtime>
</configuration>

问题是每当启动时应用程序都会崩溃并显示以下消息：

=== Pre-bind state information ===
LOG: User = ...
LOG: DisplayName = C,Version=2.0.0.0,PublicKeyToken=93a02044a09d059a
 (Fully-specified)
LOG: Appbase = file:///D:/Temp/TheApp/bin/Debug/Test/
LOG: Initial PrivatePath = NULL
Calling assembly : A,PublicKeyToken=null.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: D:TempTheAppbinDebugTestTheApp.exe.Config
LOG: Using machine configuration file from C:WindowsMicrosoft.NETFrameworkv2.0.50727configmachine.config.
LOG: Post-policy reference: C,PublicKeyToken=93a02044a09d059a
LOG: Attempting download of new URL file:///D:/Temp/TheApp/bin/Debug/Test/C.DLL.
LOG: Attempting download of new URL file:///D:/Temp/TheApp/bin/Debug/Test/C/C.DLL.
LOG: Attempting download of new URL file:///D:/Temp/TheApp/bin/Debug/Test/B/C.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Major Version
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.

问题：为什么运行时仅查看“B”文件夹？为什么不继续在A文件夹中查找正确版本的共享程序集？

EDIT1：我添加了< codeBase>标签如下所述,我知道在我的配置文件中有以下内容：

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
       <probing privatePath="B;A" />
    </assemblyBinding>
    <dependentAssembly>
       <assemblyIdentity name="C" publicKeyToken="93a02044a09d059a" /> 
       <codeBase version="1.0.0.0" href="B/C.dll"/>
       <codeBase version="2.0.0.0" href="A/C.dll"/>
    </dependentAssembly>
  </runtime>
</configuration>

问题仍然存在！