Integrating to the max...BizTalk Style

When developing Orchestrations, you are using a visual designer, which will in effect generate XLang which is handled by the BizTalk Xlang engine. Although the Xlang engine has its own language XLang, it does support some shapes (Expression shapes, Delay) which are compatible with C#. It’s also possible to call .Net assemblies from an Atomic scope, and debug these following the steps; described in this post: Debugging .Net ): Build the external C# library project Add it to the GAC Restart the Host Instance Attach the debugger to the Host instance All great stuff, additionally, you can use the Orchestration debugger ( Orchestration debugger ) which connects to the XLang scheduler, all fine and dandy. When you however, have an orchestration that directly fails, with an error you cannot comprehend, or tracking is disabled, you’re not so happy. Tracking is performed at the persistence points ( Persistence points ). An Expression shape (which does not lead to a...

Sometimes life is just cruel; you receive an error, search for the cause and are utterly frustrated when you can find the reason. I recently had a visit from this ‘good’ friend of mine: ‘Errors exist for one or more children’ Apparently it is possible that during compilation time an error occurs, and even though you solve it, the error will still occur. The error that can occur is shown in the picture below:   What i did to solve this bugger…. - open the ODX file in Notepad (important if you do not want to meet your friend encoding mismatch) - search for ‘#error’ (should be in the XLANG body() {…} ) - remove the line (shown in the screenshot below)   This worked for me, sincerely hoping that you will not use this, if so hoping that you can take the advantage of this post….