<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://dickdijkstra.com/commServ/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>BizTalk / .NET Blog</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/default.aspx</link><description>BTS.MessageType == BlogMessage</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>Interview in Automatiserings Gids</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2008/09/19/interview-in-automatiserings-gids.aspx</link><pubDate>Fri, 19 Sep 2008 13:27:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:29</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/29.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=29</wfw:commentRss><description>Recently I've been interviewed by Automatiserings Gids about fragmentation in .NET. Read the article &lt;A class="" href="http://www.automatiseringgids.nl/artikelen/2008/35/fragmentatie%20%20net%20baart%20ook%20microsoft%20zelf%20zorgen.aspx"&gt;here&lt;/A&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=29" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/.NET/default.aspx">.NET</category></item><item><title>Testing in integration solutions</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2008/03/25/testing-in-integration-solutions.aspx</link><pubDate>Tue, 25 Mar 2008 15:05:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:28</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/28.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=28</wfw:commentRss><description>I recently told something about testing and BizTalk for the BizTalk User Group and wrote an article about this subject (Dutch). Material will be online soon...&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=28" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/Testing/default.aspx">Testing</category></item><item><title>Ghostdoc</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/10/12/ghostdoc.aspx</link><pubDate>Fri, 12 Oct 2007 14:17:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:27</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/27.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=27</wfw:commentRss><description>&lt;P&gt;I thought NDoc was great, this (&lt;A href="http://www.blueonionsoftware.com/Blog.aspx?p=ca36e092-4671-49ca-9af5-5de2e0f6dc72"&gt;http://www.blueonionsoftware.com/Blog.aspx?p=ca36e092-4671-49ca-9af5-5de2e0f6dc72&lt;/A&gt;) is even better!!&lt;/P&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=27" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/.NET/default.aspx">.NET</category></item><item><title>BizTalk 2006 Best Practices Analyzer</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/09/13/biztalk-2006-best-practices-analyzer.aspx</link><pubDate>Thu, 13 Sep 2007 13:17:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:25</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/25.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=25</wfw:commentRss><description>&lt;P&gt;A really helpful &lt;A class="" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=dda047e3-408e-48ba-83f9-f397226cd6d4&amp;amp;displaylang=en"&gt;tool&lt;/A&gt; to see whether Best Practices are applied to your BizTalk solution.&lt;/P&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=25" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category></item><item><title>Exposing a BizTalk webservice that accepts generic content</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/09/07/exposing-a-biztalk-webservice-that-accepts-generic-content.aspx</link><pubDate>Fri, 07 Sep 2007 08:52:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:24</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/24.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=24</wfw:commentRss><description>&lt;P&gt;In a BizTalk HTTP messaging scenario, it's fairly common to have one port that receives all message types. Depending on the message type (and perhaps some other properties) messages are routed to different destinations. You can implement the same pattern with the SOAP adapter. Have a look at &lt;A class="" href="http://blogs.msdn.com/richardbpi/archive/2006/11/10/exposing-biztalk-web-services-that-accept-generic-content.aspx"&gt;Richard's blog&lt;/A&gt; for a complete description.&lt;/P&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=24" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category></item><item><title>The future of BizTalk / WCF / WF</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/09/07/the-future-of-biztalk-wcf-wf.aspx</link><pubDate>Fri, 07 Sep 2007 08:46:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:23</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/23.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=23</wfw:commentRss><description>A lot of guessing and many new questions in &lt;A class="" href="http://www.winterdom.com/weblog/2007/09/03/TheFutureOfBizTalkWCFWF.aspx"&gt;this good article&lt;/A&gt; by Tomas Restrepo on the future of BizTalk / WCF / WF.&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=23" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/WF/default.aspx">WF</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/WCF/default.aspx">WCF</category></item><item><title>Dragon Curve</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/09/05/dragon-curve.aspx</link><pubDate>Wed, 05 Sep 2007 13:23:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:22</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/22.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=22</wfw:commentRss><description>&lt;P&gt;&lt;IMG title="Dragon Curve" style="WIDTH:425px;HEIGHT:282px;" height=282 alt="Dragon Curve" src="http://dickdijkstra.com/files/dragon.jpg" width=425&gt;&lt;/P&gt;
&lt;P&gt;At highschool I had to write a java application that showed the dragon curve fractal. I liked the assignment at the time because of the power of recursion. I wrote a simple .NET app that does the same. Download &lt;A class="" href="http://dickdijkstra.com/files/DragonCurve.zip"&gt;here&lt;/A&gt;&lt;/P&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=22" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/.NET/default.aspx">.NET</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/Programming/default.aspx">Programming</category></item><item><title>Property Demotion</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/08/31/property-demotion.aspx</link><pubDate>Fri, 31 Aug 2007 12:51:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:21</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/21.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=21</wfw:commentRss><description>&lt;P&gt;Most people working with BizTalk have heard of property promotion, in fact property promotion is very important in CBR messaging scenarios. Property promotion makes it possible to route messages based on their content.&amp;nbsp;In short, property promotion is taking information from the message and putting it in the context of a message.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have you ever heard of property DEmotion?? This is the opposite of property PROmotion, so taking information from the context and putting it in the message. This might become handy when you for instance need the initial filename of message. This information is stored in the context, to be more specific in the element ReceivedFileName in the schema FILE.bts_file_properties in the referenced assembly Microsoft.BizTalk.GlobalPropertySchemas. How do you get this value in your output message (demotion is done in the send port - use the &lt;STRONG&gt;XMLTransmit&lt;/STRONG&gt; pipeline)?&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Right-click&amp;nbsp;the element in your schema you want to contain the ReceivedFileName value and click Promote -&amp;gt; Show Promotions.&lt;/LI&gt;
&lt;LI&gt;Add a new property schema: choose &amp;lt;your schema project&amp;gt; -&amp;gt; References -&amp;gt; Microsoft.BizTalk.GlobalPropertySchemas -&amp;gt; Schemas -&amp;gt; FILE.bts_file_properties &lt;/LI&gt;
&lt;LI&gt;Choose a proper prefix e.g. btsFileProps or something, I think ns0 is dirty&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Add your element and bind it to &amp;lt;your prefix&amp;gt;:ReceivedFileName and click ok&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Deploy your schema and test it - your output message should contain the ReceivedFileName property value if your input message has left the element to be filled&amp;nbsp;empty. Questions? Feel free to ask!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=21" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category></item><item><title>BizTalk Hotrod: Where BizTalk Meets the Road...</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/08/31/biztalk-hotrod-where-biztalk-meets-the-road.aspx</link><pubDate>Fri, 31 Aug 2007 07:38:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:20</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/20.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=20</wfw:commentRss><description>&lt;P&gt;&amp;nbsp;&lt;IMG title="Hotrod sketch" style="WIDTH:306px;HEIGHT:209px;" height=404 alt="Hotrod sketch" src="http://biztalkhotrod.com/Images/rs_sketch.jpg" width=640&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I really like the&amp;nbsp;magazines (&lt;A class="" href="http://biztalkhotrod.com/Documents/Hotrod1Q32007%20Final.pdf"&gt;issue 1&lt;/A&gt;, &lt;A class="" href="http://biztalkhotrod.com/Documents/Hotrod1Q4%202007%20Final.pdf"&gt;issue 2&lt;/A&gt;)&amp;nbsp;on the BizTalk Hotrod &lt;A class="" href="http://biztalkhotrod.com/"&gt;website&lt;/A&gt;. Both the website and the articles so far contain very good&amp;nbsp;and readable information on new BizTalk technologies. &lt;/P&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=20" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category></item><item><title>AMQP </title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/08/29/amqp.aspx</link><pubDate>Wed, 29 Aug 2007 09:15:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:19</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/19.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=19</wfw:commentRss><description>Have a look at &lt;A class="" href="https://jira.amqp.org/confluence/display/AMQP/Advanced+Message+Queuing+Protocol"&gt;this&lt;/A&gt;. AMQP is a messaging standard that looks very powerful. I wonder when a .NET / BizTalk implemention will be available. &lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=19" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/.NET/default.aspx">.NET</category></item><item><title>Schemas without namespace</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/08/21/schemas-without-namespace.aspx</link><pubDate>Tue, 21 Aug 2007 06:59:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:18</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/18.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=18</wfw:commentRss><description>It's not recommended, but sometimes you dont have a choice to use schemas without namespaces. BizTalk deals with the schemas very well, just be aware that the BTS.MessageType used in the filter will be only the rootnode, not &lt;STRONG&gt;#RootNode&lt;/STRONG&gt;.&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=18" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category></item><item><title>Working on BizTalk Solution Software Factory</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/08/17/working-on-biztalk-solution-software-factory.aspx</link><pubDate>Fri, 17 Aug 2007 10:01:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:17</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>1</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/17.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=17</wfw:commentRss><description>I'm working on a new version of the BizTalk Software Factory, enhancing the old version with functionality to create pipeline components. Futher on, the new version will contain a DSL for creating CBR solutions. Future plans are to include functionality for creating application adapters and BizTalk adapters.&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=17" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/software+factory/default.aspx">software factory</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category></item><item><title>AssemblyInfo.cs in template when compiling Guidance Automation Project</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/07/26/assemblyinfo-cs-in-template-when-compiling-guidance-automation-project.aspx</link><pubDate>Thu, 26 Jul 2007 13:30:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:16</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/16.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=16</wfw:commentRss><description>&lt;P&gt;When you're working with an Guidance Automation Project and you have template for lets say, a class library project that contains the file properties\assemblyinfo.cs, make sure you set the build action to "Content" instead of "Compile", or else you'll get an error message saying there are duplicate attributes in AssemblyInfo.cs.&amp;nbsp;You get the&amp;nbsp;error&amp;nbsp;because the GA project itself also contains an AssemblyInfo.cs file.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;P.S. Don't forget to set the "Copy To Output Directory" to "Copy if newer" for obvious reasons...&lt;/P&gt;&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=16" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/software+factory/default.aspx">software factory</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/.NET/default.aspx">.NET</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/GAT/default.aspx">GAT</category></item><item><title>Covast &amp; R2</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/07/24/covast-r2.aspx</link><pubDate>Tue, 24 Jul 2007 14:49:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:15</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/15.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=15</wfw:commentRss><description>With the coming of native EDI support in BizTalk 2006 R2, many people thought Covast would not be involved in creating EDI solutions with BizTalk. Well, that's not what's going to happen. Covast adds the very specific standards, like EDIG@S, ODETTE and EDINE. Moreover, Covast adds a nice B2B appliance called BBOT...nice!&amp;nbsp;Have a look at the &lt;A class="" href="http://www.covast.com/file/Covast-Our_value_add_on_BizTalk_Server_2006_R2.pdf"&gt;article&lt;/A&gt;.&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=15" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/BizTalk/default.aspx">BizTalk</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/EDI/default.aspx">EDI</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/Covast/default.aspx">Covast</category></item><item><title>NCover</title><link>http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/2007/07/24/ncover.aspx</link><pubDate>Tue, 24 Jul 2007 13:40:00 GMT</pubDate><guid isPermaLink="false">ded273ab-9e87-4979-8222-e4e2e46f1b46:14</guid><dc:creator>Dick Dijkstra</dc:creator><slash:comments>0</slash:comments><comments>http://dickdijkstra.com/commServ/blogs/bts_dotnet/comments/14.aspx</comments><wfw:commentRss>http://dickdijkstra.com/commServ/blogs/bts_dotnet/commentrss.aspx?PostID=14</wfw:commentRss><description>When testing your software, do you hit every line of code? Maybe you do, maybe you don't, but how can you make sure you do? Check out &lt;A class="" href="http://www.ncover.com/"&gt;this&lt;/A&gt; tool, it'll show you the level of coverage of your code.&lt;img src="http://dickdijkstra.com/commServ/aggbug.aspx?PostID=14" width="1" height="1"&gt;</description><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/Testing/default.aspx">Testing</category><category domain="http://dickdijkstra.com/commServ/blogs/bts_dotnet/archive/tags/.NET/default.aspx">.NET</category></item></channel></rss>