<?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: BizTalk Filters not Getting Imported</title>
	<atom:link href="http://winterdom.com/2008/06/biztalkfiltersnotgettingimported/feed" rel="self" type="application/rss+xml" />
	<link>http://winterdom.com/2008/06/biztalkfiltersnotgettingimported</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: Bram</title>
		<link>http://winterdom.com/2008/06/biztalkfiltersnotgettingimported/comment-page-1#comment-424</link>
		<dc:creator>Bram</dc:creator>
		<pubDate>Tue, 24 Jun 2008 12:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2008/06/biztalkfiltersnotgettingimported#comment-424</guid>
		<description>Tomas,
I have experienced the same issue, and it drove me mad as well. We solved it by using a tool called ElementTunnel, which can be downloaded as part of Scott Colestock&#039;s BizTalk Deployment Framework (on CodePlex). It allows you to manually maintain BizTalk binding files without having to fear that BizTalk won&#039;t eat it, by performing xml encoding/decoding.
Another thing with the BizTalk binding file is that I once tried to get a decent xsd for it by pointing xsd.exe at one of the types in one of the BizTalk assemblies (can&#039;t remember which one). Validating binding files just didn&#039;t work afterwards. When manually maintaining BizTalk binding files, a way to validate them would make things (a little) better.
</description>
		<content:encoded><![CDATA[<p>Tomas,<br />
I have experienced the same issue, and it drove me mad as well. We solved it by using a tool called ElementTunnel, which can be downloaded as part of Scott Colestock&#8217;s BizTalk Deployment Framework (on CodePlex). It allows you to manually maintain BizTalk binding files without having to fear that BizTalk won&#8217;t eat it, by performing xml encoding/decoding.<br />
Another thing with the BizTalk binding file is that I once tried to get a decent xsd for it by pointing xsd.exe at one of the types in one of the BizTalk assemblies (can&#8217;t remember which one). Validating binding files just didn&#8217;t work afterwards. When manually maintaining BizTalk binding files, a way to validate them would make things (a little) better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
