<?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>A customer question on Thread.Name</title><link>http://blogs.msdn.com/bclteam/archive/2003/11/11/49736.aspx</link><description>A query was raised by Ilya Ryzhenkov on Thread.Name: "What's the reason of Thread.Name property be write-once?" Ilya, the response I got was from Chris Brumme , an architect on the CLR team. Chris points out that if you care about the name of your thread,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>RE: A customer question on Thread.Name</title><link>http://blogs.msdn.com/bclteam/archive/2003/11/11/49736.aspx#49737</link><pubDate>Wed, 26 Nov 2003 13:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:49737</guid><dc:creator>Olivier Le Pichon</dc:creator><description>Yes but if you want to reuse a thread to do different kind of job (&amp;#224; la ThreadPool) it can be great to be able to modify its name.</description></item><item><title>Nommer ses threads, mais une seule fois !</title><link>http://blogs.msdn.com/bclteam/archive/2003/11/11/49736.aspx#8590394</link><pubDate>Tue, 10 Jun 2008 23:43:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8590394</guid><dc:creator>Blog d'Olivier Huet</dc:creator><description>&lt;p&gt;Pour des besoins de diagnostic, il est parfois bien pratique de donner un nom aux threads, quand ils&lt;/p&gt;
</description></item></channel></rss>