用c#编写编排
我想知道是否有任何方法可以通过代码创建/修改编排而不是绘制方框。 我知道 .odx 文件中的所有内容都会转换为 c# 代码（或非常类似的代码）。那么有没有办法修改该代码并让 biztalk 生成这些绘图呢？
由于我在 C/C# 方面的经验更多，因此代码方法对我来说比绘图方法更自然。
顺便说一句，我不是在谈论编写自定义管道或其他从编排中调用的外部类，我已经知道如何做到这一点。我真的很想通过代码来编写编排本身。
I was wondering if there is any way to create/modify an orchestration by code instead of drawing the boxes.
I know that everything gets converted to c# code(or something very similar) in the .odx file. So is there a way to modify that code and have biztalk generate those drawings instead?
Since my experience is much more in C/C#, the code approach is much more natural to me than drawing approach.
BTW, I am NOT talking about writing custom pipelines or other external classes to be called from the orchestration, I already know how to do this. I really want to code the orchestration itself by code.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
理论上，可以使用 XLang 语言编写编排
http:// /msdn.microsoft.com/en-us/library/aa577463(BTS.70).aspx
无论您在设计器中创建什么，它都会被转换为 XLang，然后XLang 被翻译为 C#。这也意味着代码甚至可以用 C# 编写，但是，因为我已经尝试反编译代码一两次 - 它太复杂了。
In theory, orchestrations can be written using the XLang language
http://msdn.microsoft.com/en-us/library/aa577463(BTS.70).aspx
Whatever you create in the designer, it gets translated to XLang and then XLang is translated to C#. This also means that the code could probably be even written in C#, however, as I've tried to decompile the code once or twice - it's just too complicated.
虽然理论上这是可能的，但我认为我宁愿挖出自己的眼睛也不愿尝试手工编写编排。 odx 文件分为两部分，xml 定义形状和布局，xlangs 代码定义描述形状的类型和函数。这与 aspx 1.1 中旧的“代码隐藏”概念类似。
这两件事如果没有彼此就没用，所以 XML 本身会布局所有形状但不会编译，并且代码本身也无法编译（尽管说实话我从未尝试过这一点）。
如果您正在寻找一种更标准化的语言来描述业务流程，您可以查看 BPEL，它由 BizTalk 支持，但话又说回来，我从未使用过此语言，因此无法进一步评论。
While in theory this is possible I think I would rather gouge my own eyes out than try to write an orchestration by hand. The odx file is in two parts, the xml defines the shapes and layout and the xlangs code defines the types and functions describing the shapes. This a similar concept to the old "code behind" in aspx 1.1.
These two things are useless without each other, so the XML by itself will layout all the shapes but will not compile, and the code by itself cannot compile either (although to be honest I have never tried this).
If you are looking for a more standardised language to describe business processes you could look at BPEL, which is supported by BizTalk, but then again I have never worked with this so could not comment further.