So you know how the actual CLR hasn't changed since .NET 2.0? That is not entirely true (i.e. the one for Vista is a different build number), especially when you consider the .NET 3.5 release. The cut a long story short, Microsoft has taken the opportunity to include a service pack for the .NET CLR 2.0, which is a great thing as we are getting fixes for some annoying bugs.

One of the changes in SP1 of the CLR is the increase of the max number of threads per CPU that the .NET ThreadPool supports. It used to be 25 per CPU and the number has now increased to 250. Richard Blewett points out how this could be a potential gotcha as more threads means more memory consumed and ... well read the post! It's something not very likely to happen, but definitely worth knowing about. Plus, he talks about what brought this change, which is always interesting to know.