I've seen stranger DateTime usage in the Web Service I'm working on. We use a nullable type too, but in this case it was a WTF because Microsoft handed us a WTF with WCF. Stranger is our code that handles a DataSet which has a DateTime column as part of an incoming web request. Whenever we get new developers on board, we watch them when they come across this piece of code. Some of them slump down in their desks and go into a trance, while some quickly walk away and wash their hands with plenty of SOAP. :) SG Aham Brahmasmi!

Nope. I'm mostly working in Silverlight, but this is backend code for a webservice, so ASP.NET. I don't see any reason to 'force' you to write bad exception handling code, ie catching Exception, then testing type. 'I'm French! Why do you think I've got this outrrrrageous accent?' Monty Python and the Holy Grail

No, you understood perfectly. I just didn't know what kind of apps you made. All the best, Dan

Well spotted, I did stop at the case mismatch there! 'As programmers go, I'm fairly social. Which still means I'm a borderline sociopath by normal standards.' Jeff Atwood

Hey, it's really a curse! My 'new' PC isn't really working well either :laugh: It's got a Kaspersky slowing it to a crawl, trying to uninstall that, but the monster comes back even after you cut its head (well, the uninstall crashed the whole PC). Then it lost its integrated network card (probably Kaspersky related), uninstall card, reboot, reinstall card. So, Visual Studio isn't yet ready to roll... Well, it's only 3pm, maybe I will get some work done today :doh: