This feed does not validate.

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.


  1. <?xml version="1.0" encoding="utf-8"?><feed version="0.3" xml:lang="en-UK" xmlns="">
  2.    <!-- X-Clacks-Overhead: GNU Terry Pratchett -->
  3. <title>carbon14 Blog</title>
  4. <link rel="alternate" type="text/html" href="" />
  5. <tagline>My blog</tagline>
  6. <generator url="" version="0.9.1">b2evolution</generator>
  7. <modified>2017-06-16T08:51:32Z</modified>
  8. <entry>
  9. <title type="text/plain" mode="xml">Bug in BizTalk LogicalAnd functoid</title>
  10. <link rel="alternate" type="text/html" href=";more=1&amp;c=1&amp;tb=1&amp;pb=1" />
  11. <author>
  12. <name>admin</name>
  13. </author>
  14. <id>;more=1&amp;c=1&amp;tb=1&amp;pb=1</id>
  15. <issued>2017-06-16T08:38:52Z</issued>
  16. <modified>2017-06-16T08:51:32Z</modified>
  17. <content type="text/html" mode="escaped"><![CDATA[ <p>While unit testing my own functoids, I came across an odd scenario where my map was working with inline C#, but if I switched to testing the external assembly version, the results were completely different. Obviously I started with the assumption that my functoid was broken, but in fact it appears that it's Microsoft's LogicalAnd functoid which is broken, and has been since BizTalk 2006.</p>
  18. <p>I must stress, that the failure only occurs when you are using the external assembly version of the functoid, which would occur only when you have set the script type preference on your map to give higher priority to the external assembly script type than the inline C# script type.  And frankly I still don't know why you would ever want to do that. But if you do, the LogicalAnd functoid is broken.</p>
  19. <p>In BizTalk 2004, the functoid used this code which works:</p>
  20. <pre><code>
  21. // Microsoft.BizTalk.BaseFunctoids.FunctoidScripts
  22. public bool LogicalAnd(string val1, string val2)
  23. {
  24. bool flag = false;
  25. try
  26. {
  27. flag = bool.Parse(val1);
  28. }
  29. catch (Exception)
  30. {
  31. if (BaseFunctoid.IsNumeric(val1))
  32. {
  33. int num = Convert.ToInt32(val1, CultureInfo.get_InvariantCulture());
  34. flag = (0 &lt; num);
  35. }
  36. else
  37. {
  38. flag = false;
  39. }
  40. }
  41. if (flag)
  42. {
  43. try
  44. {
  45. bool flag2 = bool.Parse(val2);
  46. flag = (flag &amp;&amp; flag2);
  47. }
  48. catch (Exception)
  49. {
  50. if (BaseFunctoid.IsNumeric(val2))
  51. {
  52. int num2 = Convert.ToInt32(val2, CultureInfo.get_InvariantCulture());
  53. bool flag3 = true;
  54. if (0 >= num2)
  55. {
  56. flag3 = false;
  57. }
  58. flag = (flag &amp;&amp; flag3);
  59. }
  60. else
  61. {
  62. flag = false;
  63. }
  64. }
  65. }
  66. return flag;
  67. }
  68. </code></pre> <p>
  69. but at some point, either in BizTalk 2006 or in 2006r2 they changed to this code:</p>
  70. <pre><code>// Microsoft.BizTalk.BaseFunctoids.FunctoidScripts
  71. public bool LogicalAnd(string val1, string val2)
  72. {
  73. bool flag = false;
  74. if (!bool.TryParse(val1, out flag))
  75. {
  76. if (BaseFunctoid.IsNumeric(val1))
  77. {
  78. int num = Convert.ToInt32(val1, CultureInfo.InvariantCulture);
  79. flag = (0 &lt; num);
  80. }
  81. else
  82. {
  83. flag = false;
  84. }
  85. }
  86. if (flag)
  87. {
  88. bool flag2 = false;
  89. if (!bool.TryParse(val2, out flag2))
  90. {
  91. flag = (flag &amp;&amp; flag2);
  92. }
  93. else if (BaseFunctoid.IsNumeric(val2))
  94. {
  95. int num2 = Convert.ToInt32(val2, CultureInfo.InvariantCulture);
  96. flag2 = true;
  97. if (0 >= num2)
  98. {
  99. flag2 = false;
  100. }
  101. flag = (flag &amp;&amp; flag2);
  102. }
  103. else
  104. {
  105. flag = false;
  106. }
  107. }
  108. return flag;
  109. }
  110. </code></pre> <p>
  111. The new code is cleaner, and uses the TryParse method of the Boolean, presumably to avoid the overhead of the try..catch block.   But the sense of the second parse test is the wrong way round; that second exclamation mark shouldn't be there; and as a result this function will almost always return false.</p>
  112. <p>The fact that this bug appears to have survived for a decade suggests that no-one ever chooses to prioritise external assemblies in their maps, but you never know.</p>
  113. <p>A Boolean and function should be the easiest thing to get right, and it certainly shouldn't be difficult to have unit testing this function.
  114. </p>
  115. ]]></content>
  116. </entry>
  117. <entry>
  118. <title type="text/plain" mode="xml">Unexpected Execution Order of Pipeline Components in BizTalk</title>
  119. <link rel="alternate" type="text/html" href=";more=1&amp;c=1&amp;tb=1&amp;pb=1" />
  120. <author>
  121. <name>admin</name>
  122. </author>
  123. <id>;more=1&amp;c=1&amp;tb=1&amp;pb=1</id>
  124. <issued>2016-11-28T16:26:34Z</issued>
  125. <modified>2016-11-28T16:27:10Z</modified>
  126. <content type="text/html" mode="escaped"><![CDATA[ <p>Recently I ran into an unexpected problem with a custom pipeline component which I thought had been working fine. Suddenly it stopped working, but with an unexpected workaround. Today I worked out what the problem is, and although it makes perfect sense it caught me by surprise. I can't find any mention of this gotcha elsewhere on the internet, so I thought I'd write about it here.</p>
  127. <p>Last year I wrote a custom pipeline component (Message Dump component) which optionally dumps the message body and/or the context of the message, and I use it regularly in my pipelines. Because the dumping is optional, and can be quickly controlled at runtime, I place the component in pretty much all of the pipelines that I use. When turned off, the overhead is minimal, but when you want to check what's going through any given stage of a pipeline you can quickly turn it on and get what you need.</p>
  128. <p>This year we decided that one of our pipelines should <em>always</em> dump a copy of the message body and so I created another cut down version of this component (Archive component) that didn't have the optional switch. It has just 1 configuration option which is the path to the file that should be written, and that file path can contain various macros which can be expanded from the message context.</p>
  129. <p>Everything seemed to work in the development and test environments; we went live with it and it was great. After a period of live commissioning I turned off the Message Dump components in the pipeline, and that's when it all went wrong.</p>
  130. <p class="bMore"><a href=";more=1&amp;c=1&amp;tb=1&amp;pb=1#more1211"><img src="" alt="&#61;&#62;" class="middle" /> Read more!</a></p>
  131. ]]></content>
  132. </entry>
  133. <entry>
  134. <title type="text/plain" mode="xml">If..Then..Else mapping in BizTalk</title>
  135. <link rel="alternate" type="text/html" href=";more=1&amp;c=1&amp;tb=1&amp;pb=1" />
  136. <author>
  137. <name>admin</name>
  138. </author>
  139. <id>;more=1&amp;c=1&amp;tb=1&amp;pb=1</id>
  140. <issued>2015-09-15T15:34:04Z</issued>
  141. <modified>2015-09-15T16:32:27Z</modified>
  142. <content type="text/html" mode="escaped"><![CDATA[ <p>Starting some serious development in Microsoft BizTalk 2013 and I was looking for a way to streamline some of our maps. One common place where we have clutter is in the if..then..else design pattern. Typically you want to map one element if something is true, and if it's not true, you want to map something else instead. </p>
  143. <p>BizTalk doesn't provide functoids that do that neatly, and over the years several people have commented on this; it's a problem that goes right back to at least BizTalk 2006. </p>
  144. <p>In this post I'm going to show you the custom functoids that I created to try to streamline my maps.</p>
  145. <p class="bMore"><a href=";more=1&amp;c=1&amp;tb=1&amp;pb=1#more1167"><img src="" alt="&#61;&#62;" class="middle" /> Read more!</a></p>
  146. ]]></content>
  147. </entry>
  148. <entry>
  149. <title type="text/plain" mode="xml">ISP Muppetry</title>
  150. <link rel="alternate" type="text/html" href=";more=1&amp;c=1&amp;tb=1&amp;pb=1" />
  151. <author>
  152. <name>admin</name>
  153. </author>
  154. <id>;more=1&amp;c=1&amp;tb=1&amp;pb=1</id>
  155. <issued>2007-11-09T13:09:18Z</issued>
  156. <modified>2007-11-09T13:09:18Z</modified>
  157. <content type="text/html" mode="escaped"><![CDATA[ <p>I've just had to help a friend with here broadband email service. It was working on Monday, but at some point during the week it stopped.</p>
  158. <p>It was complaining that it couldn't get a response from the POP3 server. So I double checked all the documentation and rechecked the password. No good.</p>
  159. <p>I had a look through her existing emails and discovered that she'd been sent details of a new email service that she was being moved onto. So I checked through the settings for that.<br />
  160. There were quite a few settings changes and I thought that would sort it, but no.</p>
  161. <p>So then I went to the ISPs extremely slow, and badly organised AJAX enabled website, where eventually I managed to get the help pages to open for me. There I double checked all the settings, still OK and then looked for more help.</p>
  162. <p>"Perhaps your password has become desynchronised in the move to the new service. Go to this page and change your password." It suggested.</p>
  163. <p>I eventually had to find a different computer to get through the website without the AJAX choking and then I changed the password. </p>
  164. <p>It still wasn't working.</p>
  165. <p>I logged into the provider's site again, to be sure the password was right.<br />
  166. I logged into the provider's webmail service, which I discover is now a GMail solution. </p>
  167. <p>There I find, in my friend's inbox, sent after the changeover, a new, and subtly different set of instructions on what to do to get POP3 working. Now you have to log into the webmail service and ENABLE POP3 apparently.</p>
  168. <p>IF you move someone to a new email service.<br />
  169. AND some changes are necessary for them to continue to use it as before<br />
  170. sending them instructions AFTER the changeover is NOT GOOD ENOUGH!!!
  171. </p>
  172. ]]></content>
  173. </entry>
  174. <entry>
  175. <title type="text/plain" mode="xml">Fishcakes</title>
  176. <link rel="alternate" type="text/html" href=";more=1&amp;c=1&amp;tb=1&amp;pb=1" />
  177. <author>
  178. <name>admin</name>
  179. </author>
  180. <id>;more=1&amp;c=1&amp;tb=1&amp;pb=1</id>
  181. <issued>2007-07-05T18:51:53Z</issued>
  182. <modified>2007-07-05T18:51:53Z</modified>
  183. <content type="text/html" mode="escaped"><![CDATA[ <p>I made some fishcakes yesterday, very easy and extremely tasty.</p>
  184. <p>This should make 4 fishcakes. Enough for 2 people as a main meal with a salad or a handful of chips.</p>
  185. <p>Boil some potatoes, around 250g, until tender. I used new potatoes and then peeled them, but you can use any floury potatoes and peel them first if they have thicker skins. While they were boiling, I was able to steam 180g of fish fillet above the boiling water. You can use any firm fish, cod, haddock or salmon for example. I went for coley because I had some in. It's a little darker in colour than cod, but with a similar flavour, a little less delicate.</p>
  186. <p>Take 2 handfuls of fresh parsley and blend with 15g of cold butter. Then mix with the hot potatoes and mash them with a fork until smooth. Flake the steamed fish into the mash, add two handfuls of fine breadcrumbs and combine thoroughly.</p>
  187. <p>Form the mixture into patties and then chill in the fridge for at least half an hour. They will become a good deal less sticky as the breadcrumbs absorb some of the moisture, and the cooling potato congeals.</p>
  188. <p>When you are ready to cook the fishcakes, beat an egg into a shallow bowl, dip the patties into the egg, coating both sides, and then cover them with a mixture of breadcrumbs and polenta grains. Shallow fry for a few minutes on each side until they are golden brown and the coating has become crispy. </p>
  189. <p>Serve immediately.
  190. </p>
  191. ]]></content>
  192. </entry>
  193. </feed>
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda