In my previous post (“BizTalk Orchestration – Orchestration debugging inside Visual Studio”) I explain how to debug BizTalk 2004, 2006 or R2 orchestration in Visual Studio.
So how can I do this in BizTalk 2009 version?
When compiling a BizTalk Server 2009 project in Visual Studio classes (.cs) files are generated for the BizTalk artifacts. Those files are not part of the project and have the extension ‘.cs’, e.g.: .btp.cs, .xsd.cs, .btm.cs
I was expecting also a .odx.cs file, but that is not the case. The CS file for the Orchestration is placed in “objDebugBizTalkXLang” and is called File0.cs. If you open this file you can attach this file to your BizTalk process (where the Orchestration is hosted in) and of course place a breakpoint.
Another difference is that if we have more than one orchestration, when we compile the solution, Visual Studio DON’T generate two CS files (File0.cs and File1.cs), he only generate one, and the two (or more) orchestrations code are inside the file: File0.cs
Inside this file he creates different class according to the orchestration Typename property, sample:
- sealed internal class BizTalk_Orchestration1 : Microsoft.BizTalk.XLANGs.BTXEngine.BTXService …
- sealed internal class BizTalk_Orchestration2 : Microsoft.BizTalk.XLANGs.BTXEngine.BTXService…
- And special thanks to Thiago Almeida for responded in MSDN Forum and alert me to this new feature
Tags: BizTalk | Orchestration | Debug | Visual Studio