I’m glad to confirm that the ThreadPool bug introduced in .NET 3.5 has been fixed in SP1 for .NET 3.5.
For more background information, look at these posts.
- .NET 3.5 Brings Breaking Changes to ThreadPool [defunct link: http://www.michaelckennedy.net/blog/PermaLink,guid,708ee9c0-a1fd-46e5-8fa0-b1894ad6ce0f.aspx]
- Breaking Changes in the ThreadPool: The Movie [defunct link: http://www.michaelckennedy.net/blog/PermaLink,guid,040a74fe-6ea5-46fb-b3cb-049030ffd8c3.aspx]
- Follow up on .NET 2.0 SP1 ThreadPool Bug [defunct link: http://www.michaelckennedy.net/blog/PermaLink,guid,f57cf127-7bf7-445e-bef4-14c3598f92eb.aspx]
- More on the ThreadPool Bug in .NET 2.0 SP1 [defunct link: http://www.michaelckennedy.net/blog/2008/04/17/MoreOnTheThreadPoolBugInNET20SP1.aspx]
Now go forth and create some threads!
