Unexpected bindings reset on BizTalk 2009
问题 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. 回答1: It happens because it tries to apply a cached binding after you have deployed. Sometimes it doesn't correctly update the cached binding