<?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>Private Data Members</title><link>http://blogs.msdn.com/drnick/archive/2008/05/05/private-data-members.aspx</link><description>Why does a data contract with private or internal members generate a proxy with public fields? The obvious answer is that the representation for data contracts doesn't contain information about member visibility but that just leads to the question of</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Messaging Additions in Orcas, Part 4</title><link>http://blogs.msdn.com/drnick/archive/2008/05/05/private-data-members.aspx#8460808</link><pubDate>Mon, 05 May 2008 19:19:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8460808</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>&lt;p&gt;Today wraps up the series on detailed messaging changes in Orcas. You can get the whole series here as&lt;/p&gt;
</description></item></channel></rss>