C# 使用WCF和ServiceModelEx服务总线的奇怪行为

我正在使用ServiceModelEx的服务总线部分。（并使用AppFabric自动启动WCF服务）。我有一些奇怪的行为

基本上，我第一次调用服务总线时，所有正确的事件都会触发整个链（通过查看数据库和记录的值进行验证）

但在随后的通话中，什么都没有发生。就好像这些事件永远不会发生

.svclogs没有显示任何有用的内容，事实上，它们甚至没有注册后续事件

但是，windows事件日志确实显示订阅到总线的每个服务的以下错误：

WebHost failed to process a request.
 Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/777031
 Exception: System.ServiceModel.ServiceActivationException: The service '/AcmeWidgets.WidgetFactory.Subscribers.WidgetBuilder/BuildService.svc' cannot be activated due to an exception during compilation.  The exception message is: The type 'AcmeWidgets.WidgetFactory.Subscribers.WidgetBuilder.BuildService', provided as the Service attribute value in the ServiceHost directive, or provided in the configuration element system.serviceModel/serviceHostingEnvironment/serviceActivations could not be found.. ---> System.InvalidOperationException: The type 'AcmeWidgets.WidgetFactory.Subscribers.WidgetBuilder.BuildService', provided as the Service attribute value in the ServiceHost directive, or provided in the configuration element system.serviceModel/serviceHostingEnvironment/serviceActivations could not be found.
   at System.ServiceModel.Activation.ServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
 Process Name: w3wp
 Process ID: 3052

我知道服务属性值是正确的，显然是因为它第一次运行时是正确的

有什么想法吗

---

编辑1：为了增加这种奇怪的行为，如果我在Visual Studio中“重建”解决方案，对总线的第一次调用会起作用，所有事件都会触发，然后所有后续调用都会失败，那么这里显示堆栈跟踪的代码路径也不是特定于服务总线的。这是一个激活错误。在我看来，这里似乎存在类型加载错误。我想先用fuslogvw看看这个