意外的绑定在BizTalk 2009上重置 [英] Unexpected bindings reset on BizTalk 2009

问题描述

我在BizTalk 2009上使用了许多应用程序.我多次注意到，在随机应用程序中添加资源(.dll)之后，精确应用程序的所有绑定(自定义管道)都完全重置为早期的先前状态.

I use many application on BizTalk 2009. I have noticed many times that, after a resource add (.dll) in a random application, all the bindings (custom pipelines) of a precise application totally reset to an early previous state.

我真的很好奇为什么会这样.但是我还需要一种解决方案来停止这种行为或自动解决此问题.

I'm really curious of why this happens. But I also need a solution to stop that behavior or resolve automatically this problem.

推荐答案

之所以会发生，是因为它在部署后会尝试应用缓存的绑定.有时，它无法正确更新缓存的绑定，因此使用了陈旧的副本.如下所述，清除这些缓存的副本会在短期内有所帮助，但通常会回来.

It happens because it tries to apply a cached binding after you have deployed. Sometimes it doesn't correctly update the cached binding and so a stale copy is used. As per below, clearing these cached copies out helps in the short term, but often it comes back.

来自

Visual Studio在部署BizTalk应用程序时使用缓存的绑定文件.删除这些缓存的绑定文件将导致干净"部署，该部署应解决所有与绑定相关的部署错误.这些文件存储在％APPDATA％\ Microsoft \ BizTalk Server \ Deployment \ BindingFiles中.清除此目录的内容应该可以解决与缓存的绑定有关的所有部署问题.

Visual Studio uses cached binding files when deploying BizTalk applications. Removing these cached binding files will result in a ‘clean’ deployment that should resolve any binding related deployment errors. The files are stored in %APPDATA%\Microsoft\BizTalk Server\Deployment\BindingFiles. Clearing the contents of this directory should resolve any deployment issues related to cached bindings.

另请参见导入MSI更改端口管道

这篇关于意外的绑定在BizTalk 2009上重置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！