<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Fix Message Encoding Custom Pipeline Component Sample</title>
	<atom:link href="http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample/feed" rel="self" type="application/rss+xml" />
	<link>http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample</link>
	<description>by dæmons be driven</description>
	<lastBuildDate>Tue, 16 Mar 2010 06:33:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample/comment-page-1#comment-1125</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Fri, 11 Sep 2009 02:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample#comment-1125</guid>
		<description>@Jay: It might depend on how exactly you&#039;re sending the message over MSMQ (I&#039;ve talked about this before, see http://winterdom.com/2008/04/biztalk2006msmqandbiztalk2002 ). Also, to be honest, I don&#039;t know if the EDI Disassembler pays attention to the same charset property that the XML and FF disassemblers do, that&#039;s something I&#039;d need to look into.</description>
		<content:encoded><![CDATA[<p>@Jay: It might depend on how exactly you&#8217;re sending the message over MSMQ (I&#8217;ve talked about this before, see <a href="http://winterdom.com/2008/04/biztalk2006msmqandbiztalk2002" rel="nofollow">http://winterdom.com/2008/04/biztalk2006msmqandbiztalk2002</a> ). Also, to be honest, I don&#8217;t know if the EDI Disassembler pays attention to the same charset property that the XML and FF disassemblers do, that&#8217;s something I&#8217;d need to look into.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample/comment-page-1#comment-1122</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Wed, 09 Sep 2009 20:53:13 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample#comment-1122</guid>
		<description>I am Using your Fix message encoding tool at a decode stage while I am using EDI disassembler on disassemble stage but I am getting same generic message (no disassemble stage can recognize the data ). I can use the same body of a message write that in a file and use FILE as a transport, that work just fine but if I try to pick same message using MSMQ with EDI disassembler pipeline, it gives me a same error each time.I am not sure which Encoding I should pick though I have tried almost all which make sense to me.</description>
		<content:encoded><![CDATA[<p>I am Using your Fix message encoding tool at a decode stage while I am using EDI disassembler on disassemble stage but I am getting same generic message (no disassemble stage can recognize the data ). I can use the same body of a message write that in a file and use FILE as a transport, that work just fine but if I try to pick same message using MSMQ with EDI disassembler pipeline, it gives me a same error each time.I am not sure which Encoding I should pick though I have tried almost all which make sense to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample/comment-page-1#comment-1084</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Wed, 12 Aug 2009 02:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample#comment-1084</guid>
		<description>@Sachin: To be honest, I haven&#039;t tried it myself (or touched that code in a while), as I don&#039;t have a 64-bit biztalk installation at the moment. However, if you&#039;ve got an error message or any info about reproducing the problem, let me know (here or an email would do fine) and I&#039;ll see what I can do to help you resolve it.</description>
		<content:encoded><![CDATA[<p>@Sachin: To be honest, I haven&#8217;t tried it myself (or touched that code in a while), as I don&#8217;t have a 64-bit biztalk installation at the moment. However, if you&#8217;ve got an error message or any info about reproducing the problem, let me know (here or an email would do fine) and I&#8217;ll see what I can do to help you resolve it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sachin</title>
		<link>http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample/comment-page-1#comment-1079</link>
		<dc:creator>Sachin</dc:creator>
		<pubDate>Tue, 11 Aug 2009 09:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample#comment-1079</guid>
		<description>Hi Tomas,

Will this Dll work on 64 - bit machine. It works fine with 32- bit machine but we have found problems executing it on 64 bit.

Can you please let us know about this.

Thanks in advance.

Regards,
Sachin.</description>
		<content:encoded><![CDATA[<p>Hi Tomas,</p>
<p>Will this Dll work on 64 &#8211; bit machine. It works fine with 32- bit machine but we have found problems executing it on 64 bit.</p>
<p>Can you please let us know about this.</p>
<p>Thanks in advance.</p>
<p>Regards,<br />
Sachin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample/comment-page-1#comment-1010</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Thu, 02 Jul 2009 12:41:15 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample#comment-1010</guid>
		<description>It will not transcode the message; all it does is make sure BizTalk knows what encoding it is in so that it can decode it appropriately.</description>
		<content:encoded><![CDATA[<p>It will not transcode the message; all it does is make sure BizTalk knows what encoding it is in so that it can decode it appropriately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Smithesh</title>
		<link>http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample/comment-page-1#comment-1008</link>
		<dc:creator>Smithesh</dc:creator>
		<pubDate>Thu, 02 Jul 2009 07:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2006/01/fixmessageencodingcustompipelinecomponentsample#comment-1008</guid>
		<description>Hi Tomas
Will this component encode from one encoding format to another. For eg from SHIFT- JIS to EBCDIK(Katakana).
Or it will just set the encoding type that is used in the message. Please give a reply.
Thanks
Smithesh</description>
		<content:encoded><![CDATA[<p>Hi Tomas<br />
Will this component encode from one encoding format to another. For eg from SHIFT- JIS to EBCDIK(Katakana).<br />
Or it will just set the encoding type that is used in the message. Please give a reply.<br />
Thanks<br />
Smithesh</p>
]]></content:encoded>
	</item>
</channel>
</rss>
