I usually try to stay on the topic of .Net, but this is just too funny not to share -- and what the heck it is Friday. A friend of mine stopped by my house a few weeks ago and we were looking at a database issue (you know, the usual things people do when house guests drop by), we solved the problem, talked a bit, and then he left.
The next day I got an email from him asking if he left his cell phone at my house; the last time he remembers having the phone was when he dropped by. I couldn't find the phone and he figured he lost it somewhere and would have to buy a new one.
I just got this email from him:
I found my phone. Evidently I set it on the coffee table when I got home and the dog ate it - no kidding. It is no longer functional.
Even though I can piece the puzzle together fairly well on my own, I'm very eager to get the whole story. I'm full of questions like what went on in the dog's stomach when people called his cell phone? Was it set to ring or vibrate?
Something to think about for the weekend.
For those of you on the edge of your seats after the cliff-hanger ending to my post about Web Service errors when DataSets contain Error rows (HasErrors = true), I'm happy to report the results of our contact with Microsoft about the issue. After weaving through automated phone trees and navigating the layers of friendly customer service personnel, the fix to the issue is due out in Service Pack 1 of the .Net Framework 1.1. The Service Pack isn't going to be officially available for a month or two, but for customers needing a solution to the Web Service issue I encountered, you can download the 1.1.4322.918 version of System.Data.Dll (replacing 1.1.4322.573 that shipped with Framework 1.1) from Microsoft -- just contact them to get it (I suppose I could share the installer files if you really needed them, but I'm thinking MSFT would rather you got it from them directly).
After the telephone leg-work with Microsoft, rather than install the HotFix on all the various machines, I think we're just going forward with the SOAP Serialization work-around I outlined in the previous post. Just the same, it's good to know a long term solution is in the works from the good folks in Redmond.