Biztalk部署/构建问题
有没有人曾经担心过 BizTalk 有很多烦人的部署/构建问题。
例如，如果我使用 C# 程序集类来构建/部署，我经常会收到 sgen.exe 错误，如果我从程序集中删除它们，这些错误就会得到修复，但是某些依赖项会再次出现问题，这意味着我必须重建它并且重新启动 Visual Studio，因为否则它们不会触发程序集。是的，我总是使用构建事件命令：
“C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /i $(目标文件名)
我在构建时还遇到了很多序列化字符串或布尔值等问题，这些问题在我重新启动 Visual Studio 解决方案后也得到了修复。
此外，当您想要导入 .msi 文件时，您必须取消登记并取消登记。删除所有正在运行的实例以使其正确部署。
我们不要忘记重新启动主机实例，这是 Visual Studio 项目上的一个选项，但几乎不起作用，因此手动重新启动主机实例已不再是例行公事。
让我们面对现实吧，还有很多其他的事情也在不断增加，比如参考问题等，我相信在一天的工作后我能想到更多的问题。
有人对这些问题有一些技巧吗？因为我每小时都会遇到他们。我只是想知道其他人是否也遇到过这些问题并且可能解决了其中的一些问题。
Has anyone ever bothered about the fact that BizTalk has a lot of annoying deployment/building problems.
For example if I use c# assembly classes to be build/deployed I regularly get sgen.exe errors, which get fixed if I remove them from my assembly, however then some dependencies are giving problems again, which then means I have to rebuild it and restart visual studio because they don't trigger the assemblies otherwise. And yes I always use the build event command:
"C:\Program Files\Microsoft Visual
Studio 8\SDK\v2.0\Bin\gacutil.exe" /i
$(TargetFileName)
I also experience a lot of problems wwith serializing String or Booleans etc while building, which also become fixed after I restart my visual studio solution.
Also when you want to import an .msi file you have to unenlist & remove all running instances to have it deployed decently.
And let's not forget about restarting your host instances, which is an option on your visual studio project but barely ever works so manually restarting your host instances has become more than a routine.
Let's face it, there's a lot of other things which also keep on rising like references problems etc, and I'm sure I can think of a couple more after a day of work.
Does anyone have some tricks regarding these issues? Because I encounter them hourly. I was just wondering if other people encountered these too and maybe solved a couple of these issues.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
关于重新启动主机实例，我发现以下“bts-reset”PowerShell 脚本非常有用：
http://winterdom.com/2006/09/btsresetwithpowershell
它不能解决问题，但它的使用速度比从 BizTalk 管理控制台重新启动主机实例要快。
否则，我同意你的观点，即部署确实太复杂了（特别是当你有多个项目/应用程序并且它们之间存在依赖关系时），但我唯一的“解决方案”是仔细分解你的项目/应用程序，以最大限度地减少问题。
About restarting host instances, I have found the following "bts-reset" PowerShell script to be extremely useful:
http://winterdom.com/2006/09/btsresetwithpowershell
It doesn't solve the problem, but it's faster to use than restarting host instances from the BizTalk admin console.
Otherwise, I agree with you that deployment is really too complex (especially when you have multiple projects/applications with dependencies between them), but the only "solution" I have is to carefully break down your projects/applications in a way that will minimize the problem.
我们昨天安装了 BizTalk SP1。性能提升了很多！过去，开始我们的编排需要很长时间。现在只需要几秒钟！
We installed SP1 for BizTalk yesterday. The performance has improved a lot! Starting our orchestrations used to take ages. Only takes a couple of seconds now!