Note that there are some explanatory texts on larger screens.

plurals
  1. POBizTalk testing maps with multiple input xml or is it Inline C# that is the problem?
    text
    copied!<p>Can anyone explain how to get unit tests of BizTalk maps with multiple inputs to work?</p> <p>I've been happily using the examples on Michael Stephenson <a href="http://geekswithblogs.net/michaelstephenson/archive/2008/03/30/120851.aspx" rel="nofollow noreferrer">blog</a> to test my maps, but I've just tried my first multiple input map and it's failing :-(</p> <p>I've used the VS2005 "Test Map" to first generate an input instance with the two input messages, then used varieties of that file as test inputs ...</p> <pre><code>&lt;ns0:Root xmlns:ns0="http://schemas.microsoft.com/BizTalk/2003/aggschema"&gt; &lt;InputMessagePart_0&gt; ... &lt;/InputMessagePart_0&gt; &lt;InputMessagePart_1&gt; ... &lt;/InputMessagePart_1&gt; &lt;/ns0:Root&gt; </code></pre> <p>These test messages generate the expected output when I use the VS Test Map, but a section is missing when I try the unit tests. </p> <p>The only thing I can think of is the map has some functoids in ... <em>Scripting, Table Extractor and Table Looping</em> ... </p> <p>The unit test calls the StreamingTransform.ScalableTransform ...</p> <pre><code>// This is the BizTalk Server 2006 way of calling mapInstance.StreamingTransform.Transform(inputStream, mapInstance.TransformArgs, outputStream, resolver); // This is the R2 way of calling XmlReader xmlRdr = new XmlTextReader(inputStream); mapInstance.StreamingTransform.ScalableTransform(xmlRdr, mapInstance.TransformArgs, outputStream, resolver, whitespaceCorrect); </code></pre> <p>and the alternative approach of using the Transform.Transform doesn't work either ...</p> <pre><code>XPathDocument doc = new XPathDocument(inputStream); mapInstance.Transform.Transform(doc, mapInstance.TransformArgs, outputStream); </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload