Nice quote

Pleasantly I'm the customer, so it's OK, but now that I've got the
direction to head to get it done otherwise, I can dig into THAT
instead.

Thanks to Ken for his digging about.


Dan Mitchell wrote:
"Ken Slovak - [MVP - Outlook]" wrote in
:
I surely would not want to use CDO 1.21 with .NET code. It's not that
it's unsupported, most of what I do is unsupported. It's that the code
may blow up at any time for any reason and usually at a client site
and no one would be able to support you or the code or fix it.

To quote from microsoft, talking about this a while ago:

"It's the sort of thing that'll mostly work. It'll work while you're
writing it. Then it'll work while you're testing it. It'll work while your
customer is evaluating it. Then as soon as the customer deploys it - BAM!
That's when it'll decide to start having problems. And Microsoft ain't
gonna help you with it, since we told you not to do it in the first place.
"

There are certainly lots of people using .Net with CDO1.21 and even
Extended MAPI, and I suspect most of them are having no problems because
of it -- but that doesn't mean they never will.

-- dan