The above exception came up quite unexpectedly at a customer yesterday. WTF? This method certainly exists on my machine, and every other machine we tested on up until now? How can a core .NET function not exist?
It turns out, that there are some overloads to WaitOne that were only introduced in SP1 of .NET 3.5. If you don’t have SP1, you don’t have the overloads. Luckily, SP1 was a requirement already, so it was just a matter of installing it. But I would not have expected something like that from a service pack release. Nasty!!!
References:
Watch out for those WaitOne() overloads (when you need backwards …
WaitHandle.WaitOne Method (Int32) (System.Threading)
Comments are closed on this post.