<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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>A custom BizTalk 2004 disassembling pipeline component (1)</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx</link><description>Part 1 Part 2 Part 3 There are many different format of business documents. Recently, a post on microsoft.public.biztalk.nonxml caught my attention. The author receives a flat file with name/value pairs organized in tables. The flat file looks like: Table:</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>A custom BizTalk 2004 disassembling pipeline component (1)</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx#157522</link><pubDate>Thu, 17 Jun 2004 00:11:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:157522</guid><dc:creator>Gilles' WebLog</dc:creator><description /></item><item><title>A custom BizTalk 2004 disassembling pipeline component (2)</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx#157525</link><pubDate>Thu, 17 Jun 2004 00:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:157525</guid><dc:creator>Gilles' WebLog</dc:creator><description /></item><item><title>A custom BizTalk 2004 disassembling pipeline component (3)</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx#157527</link><pubDate>Thu, 17 Jun 2004 00:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:157527</guid><dc:creator>Gilles' WebLog</dc:creator><description /></item><item><title>The eXcel files: Do not use Office Object Model when processing Office documents with BizTalk 2004</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx#167904</link><pubDate>Mon, 28 Jun 2004 19:36:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:167904</guid><dc:creator>Gilles' WebLog</dc:creator><description /></item><item><title>Custom disassembling and orchestration: Could not find a matching subscription for the message?</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx#178705</link><pubDate>Fri, 09 Jul 2004 22:59:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:178705</guid><dc:creator>Gilles' WebLog</dc:creator><description /></item><item><title>re: A custom BizTalk 2004 disassembling pipeline component (1)</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx#199593</link><pubDate>Wed, 28 Jul 2004 14:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:199593</guid><dc:creator>xz_king</dc:creator><description>I am a beginer of BTS , Can I get the source project of this section ?&lt;br&gt;Thank you.&lt;br&gt;xz_king@sohu.com</description></item><item><title>re: A custom BizTalk 2004 disassembling pipeline component (1)</title><link>http://blogs.msdn.com/gzunino/archive/2004/06/13/154819.aspx#199711</link><pubDate>Wed, 28 Jul 2004 15:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:199711</guid><dc:creator>Gilles</dc:creator><description>xz_king: The source code is here. This article has three parts, you can just copy all the code from all parts, put it into a C# file and you get the source.&lt;br&gt;&lt;br&gt;Alternatively, you can just copy the &amp;quot;GetNext()&amp;quot; and &amp;quot;Execute()&amp;quot; methods and paste them in the sample &amp;quot;FixMsg&amp;quot; sample that ships with the SDK.&lt;br&gt;&lt;br&gt;Moreover, my archive contains other pipelines, with the full solution. See them at: &lt;a target="_new" href="http://weblogs.asp.net/gzunino/category/5287.aspx?Show=All"&gt;http://weblogs.asp.net/gzunino/category/5287.aspx?Show=All&lt;/a&gt;</description></item></channel></rss>