<?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>Complex Types Serialized to the Wrong Namespace by WCF</title><link>http://blogs.msdn.com/kevinha/archive/2007/07/27/complex-types-serialized-to-the-wrong-namespace-by-wcf.aspx</link><description>Have you recently tried to migrate an existing ASMX Web service to Windows Communication Foundation, and discovered that the complex types you've so lovingly hand-crafted for the XmlSerializer don't work the way you expect? Are you having to resort to</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title> Kevin W Hammond Complex Types Serialized to the Wrong Namespace by WCF | Cellulite Creams</title><link>http://blogs.msdn.com/kevinha/archive/2007/07/27/complex-types-serialized-to-the-wrong-namespace-by-wcf.aspx#9720326</link><pubDate>Wed, 10 Jun 2009 04:22:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9720326</guid><dc:creator> Kevin W Hammond Complex Types Serialized to the Wrong Namespace by WCF | Cellulite Creams</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://cellulitecreamsite.info/story.php?id=9488"&gt;http://cellulitecreamsite.info/story.php?id=9488&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>