<?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>System Types in Metadata</title><link>http://blogs.msdn.com/drnick/archive/2008/08/05/system-types-in-metadata.aspx</link><description>It's bad practice to use system types when defining an operation contract. A system type is often a complex composition of primitive types that has no direct analog in other implementations. By using a system type, you bind your service to the particular</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Avoiding Address Filters</title><link>http://blogs.msdn.com/drnick/archive/2008/08/05/system-types-in-metadata.aspx#8836311</link><pubDate>Wed, 06 Aug 2008 09:47:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8836311</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>&lt;p&gt;The address filter mode that we looked at last time solved the problem of funneling all of the messages&lt;/p&gt;
</description></item><item><title>re: System Types in Metadata</title><link>http://blogs.msdn.com/drnick/archive/2008/08/05/system-types-in-metadata.aspx#8845208</link><pubDate>Sat, 09 Aug 2008 21:55:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8845208</guid><dc:creator>Tanveer Badar</dc:creator><description>&lt;p&gt;An inaccurate heuristic would be to filter anything residing in a namespace beginning with System., MS. or Microsoft. prefix.&lt;/p&gt;
</description></item></channel></rss>