<?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>Interop-debugging fails when using more than 63 TLS slots</title><link>http://blogs.msdn.com/jmstall/archive/2007/09/25/interop-debugging-fails-when-using-more-than-63-tls-slots.aspx</link><description>Here's a Public Service Announcement: Interop-debugging may hang if the debuggee uses more than 63 native Thread Local-Storage slots and then loads the CLR. KB939969 has more details, including three workarounds. This is fixed in Orcas, so only applies</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Techy News Blog &amp;raquo; Interop-debugging fails when using more than 63 TLS slots</title><link>http://blogs.msdn.com/jmstall/archive/2007/09/25/interop-debugging-fails-when-using-more-than-63-tls-slots.aspx#5131926</link><pubDate>Wed, 26 Sep 2007 03:25:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5131926</guid><dc:creator>Techy News Blog » Interop-debugging fails when using more than 63 TLS slots</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.artofbam.com/wordpress/?p=2930"&gt;http://www.artofbam.com/wordpress/?p=2930&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Interop-debugging fails when using more than 63 TLS slots</title><link>http://blogs.msdn.com/jmstall/archive/2007/09/25/interop-debugging-fails-when-using-more-than-63-tls-slots.aspx#5192933</link><pubDate>Sat, 29 Sep 2007 01:29:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5192933</guid><dc:creator>Pawel Pabich</dc:creator><description>&lt;p&gt;&amp;quot;This is fixed in Orcas, so only applies to pre-Orcas runtimes (like .NET 2.0).&amp;quot;&lt;/p&gt;
&lt;p&gt;As far as I know Orcas still uses the same runtime as VS 2005 does. The only difference is &amp;nbsp;related to the libraries that are part of BCL. Or &amp;nbsp;I'm missing something?&lt;/p&gt;</description></item><item><title>re: Interop-debugging fails when using more than 63 TLS slots</title><link>http://blogs.msdn.com/jmstall/archive/2007/09/25/interop-debugging-fails-when-using-more-than-63-tls-slots.aspx#5203437</link><pubDate>Sun, 30 Sep 2007 00:47:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5203437</guid><dc:creator>jmstall</dc:creator><description>&lt;p&gt;Orcas includes a service pack to the VS2005 runtime. This fix is in that service pack.&lt;/p&gt;
</description></item></channel></rss>