Lucene，MoreLikeThis的替代品？(Lucene, Alternatives to MoreLikeThis?)

 据推测，在interfaces.dll中定义并由项目A实现的接口没有改变？ 也许其他项目刚刚添加了新界面。 
 
 你可能在这里有一个普通的旧的.NET DLL版本问题。 项目A（A.exe？）是针对interfaces.dll版本1.0.0.0编译的，并且此信息存储在A.exe的元数据中。 当您更新interfaces.dll到1.0.0.1时，A.exe无法加载它。 如果新的DLL是向后兼容的（它确实必须让你的强制转换工作），那么你可以提供一个策略文件告诉运行时加载器这种兼容性。 例如： 
 
<?xml version ="1.0"?>
<configuration>
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
        <assemblyIdentity name="interfaces" culture="neutral" publicKeyToken="null"/>
        <bindingRedirect oldVersion="1.0.0.0-1.0.0.1" newVersion="1.0.0.1"/>
    </dependentAssembly>
    </assemblyBinding>
</runtime>
</configuration>
 
 这告诉加载程序，如果程序集试图在1.0.0.0和1.0.0.1之间加载任何版本的interfaces.dll，则可以接受版本1.0.0.1。 在您的DLL之后使用标准模式命名该文件： policy.1.0.interfaces.xml 。 然后把它放在与A.exe相同的目录下（我想）。 
 
 或者，如果您没有更改interfaces.dll的版本号（您确实应该这样做），那么您可能会遇到不同的问题。 如果你有两个程序集的身份相同，但它们实际上不是相同的程序集，那么一旦运行时加载程序加载了其中的一个程序集，它将永远不会加载第二个程序集。 有更多的细节，但因为我认为这不太可能是你的问题，我现在不会进入他们的问题。 

Presumably the interfaces defined in interfaces.dll and implemented by project A haven't changed? Maybe the other projects have just added new interfaces.
 
You might have a plain old .NET DLL versioning issue here. Project A (A.exe?) is compiled against interfaces.dll version 1.0.0.0, and this information is stored in A.exe's metadata. When you update interfaces.dll to 1.0.0.1, A.exe can't load it. If the new DLL is backwards compatible (which it really must be for your casts to work) then you can supply a policy file that tells the runtime loader about this compatibility. For example:
 
<?xml version ="1.0"?>
<configuration>
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
        <assemblyIdentity name="interfaces" culture="neutral" publicKeyToken="null"/>
        <bindingRedirect oldVersion="1.0.0.0-1.0.0.1" newVersion="1.0.0.1"/>
    </dependentAssembly>
    </assemblyBinding>
</runtime>
</configuration>
 
This tells the loader that if an assembly tries to load any version of interfaces.dll between 1.0.0.0 and 1.0.0.1, then version 1.0.0.1 is acceptable. Name this file after your DLL, using a standard pattern: policy.1.0.interfaces.xml. Then put it in the same directory as your A.exe (I think.)
 
Alternatively, if you haven't changed the version number of interfaces.dll (which you really should) then you might have a different problem. If you've got two assemblies whose identities are the same but they're not actually the same assemblies, then once the runtime loader has loaded one of them it will never load the second. There are more details, but since I reckon this is unlikely to be your problem I won't go into them right now.