BizTalk 2016 Redeploy和Orchestration绑定 [英] BizTalk 2016 Redeploy and Orchestration bindings

问题描述

我正在进行"全面升级"因为我创建了一个新的BT服务器，用于2016年从2013服务器迁移，在TFS中分支我们的BT项目，并重建它们并部署到新的2016服务器。 2016年重建了所有港口和地点，以确保
我连续吃了所有的鸭子。除了业务流程从VS部署后变为未绑定之外，所有配置均已正常运行。我为项目启用了redeploy选项。但它没有向我的绑定文件添加任何编排信息到
保存然后在部署程序集后重新绑定

I am doing a "clean upgrade" in that I created a new BT server for 2016 to migrate from the 2013 server, branched our BT projects in TFS, and rebuilt them and deployed to the new 2016 server. Recreated all ports and locations in 2016 to make sure I had all my ducks in a row. All is configured and going well except for the orchestrations becoming unbound AFTER a deployment from VS. I have the redeploy option turned on for the projects. But it doesn't add any orchestration info to my binding files to save and then rebind after deploying the assembly

我没有更改程序集的版本号（至少不要手动）所以它不应该是问题。 

I'm not changing the version number for assemblies (at least not manually) so it shouldn't be problem. 

当它尝试使用绑定文件重新绑定时，它来自日志。

This is from the log when it tries to rebind using the binding file.

推荐答案

我已经尝试从Deployment文件夹中清除我的绑定文件没有帮助。

I already tried clearing my binding files from Deployment folder and it didn't help.

这篇关于BizTalk 2016 Redeploy和Orchestration绑定的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！