Quoted: Did you know you can use the power of the GPU to process data in .NET? A new Microsoft research project, called Accelator, exposes a .NET library for performing parallel data processing using a computer's GPU. The library translates the data-parallel operations on-the-fly to optimized GPU pixel shader code and API calls. Accelerator is a .NET 2.

Very useful information on why Monitor.Wait / Monitor.Pulse doesn't always work as expected. I've found that in practice things work fine unless the thread which pulses is in the ready state queue, where it seems to consistently get boosted. Nonetheless, the loop around Wait() is necessary in all cases. Great article.

Great article on a major gotcha for client-side .NET code (on Windows) which talks to a network.

Quoted: One of the issues in the .NET Framework 1.1 proxy support is that when the registry is read, the automatic configuration part of the proxy settings is ignored. Only the static portion of the proxy settings are read. However, if the default proxy settings in Internet Explorer are configured for automatic detection and static settings are not populated, the result is that Internet Explorer seems to download the resources correctly, while applications using the .NET Framework 1.1 get an exception that reads, "The underlying connection was closed: The remote name could not be resolved."