jh71283 said:
blowdart said:
*snip*
Pretty sure, the code in question has been untouched for months, and has never had a problem.
If you've recently installed .NET Framework 2.0 SP1 or switched to .NET Framework 3.5, then it's likely the problem has always been lurking, but previously went unnoticed.