<?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>Using Call Context Initializers for Cleanup</title><link>http://blogs.msdn.com/drnick/archive/2008/02/25/using-call-context-initializers-for-cleanup.aspx</link><description>I'm using framework features that have thread-local settings. These settings then get leaked to other client calls. How can I stop this from happening? The problem here is that WCF doesn't know about these thread-local setting changes that you've made</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Interesting Finds: February 25, 2008</title><link>http://blogs.msdn.com/drnick/archive/2008/02/25/using-call-context-initializers-for-cleanup.aspx#7893165</link><pubDate>Mon, 25 Feb 2008 17:44:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7893165</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>DataMember Best Practices</title><link>http://blogs.msdn.com/drnick/archive/2008/02/25/using-call-context-initializers-for-cleanup.aspx#7895062</link><pubDate>Mon, 25 Feb 2008 21:18:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7895062</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>&lt;p&gt;I was asked to share a list of best practices I wrote for data contracts and data members so here it&lt;/p&gt;
</description></item></channel></rss>