"Ken Slovak - [MVP - Outlook]" wrote in
:
Dan, you really like that quote from Stephen Griffin, don't you? g

Yup.. Original link is:

http://groups.google.com/group/micro...rammer.messagi
ng/msg/20149ae3de2f4920?hl=en&

It's unfortunate that they didn't get the manpower (or whatever it was)
to support CDO1.21/ExMAPI with .Net, certainly.

And it's a bit unfortunate that there's enough things out there to make
it look as if it'll work, and the only way to find out that it won't is
either to search googlegroups to see if someone has already asked the
same question (fx: collapses in fit of laughter) or to go hunting
around the KB.

Heck, _I_ don't search the KB before writing code just in case there's
an article in there that says "don't do X" -- partly because searching
the KB is generally a loss, and partly because I'll assume things work
until I find otherwise.

So explaining in great detail why mixing these things up isn't a good
plan seems like the best bet to make sure the message gets across -- the
KB article just says "this isn't supported", but not really why it's not
supported..

-- dan

I usually assume if the KB says something isn't documented or supported that
it just means some extra detective work on my part g. So much of what I do
is completely undocumented anyway I'm used to it.

According to my conversations with the PM who owns CDO there was never any
intention of making CDO .NET compliant. It's being deprecated.

Remember Mindy's XSO and all the other "wunder-API's" we were going to have
instead of having to use CDO or MAPI? And EX was going to move to SQL
Server, so no need to ensure compliance for MAPI and .NET. That's my guess
for EX MAPI, plus all those years of the Exchange team saying "Exchange is
not a development platform".

Just one more reason to use Redemption...

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Dan Mitchell" wrote in message
8.16...
"Ken Slovak - [MVP - Outlook]" wrote in
:
Dan, you really like that quote from Stephen Griffin, don't you? g

Yup.. Original link is:

http://groups.google.com/group/micro...rammer.messagi
ng/msg/20149ae3de2f4920?hl=en&

It's unfortunate that they didn't get the manpower (or whatever it was)
to support CDO1.21/ExMAPI with .Net, certainly.

And it's a bit unfortunate that there's enough things out there to make
it look as if it'll work, and the only way to find out that it won't is
either to search googlegroups to see if someone has already asked the
same question (fx: collapses in fit of laughter) or to go hunting
around the KB.

Heck, _I_ don't search the KB before writing code just in case there's
an article in there that says "don't do X" -- partly because searching
the KB is generally a loss, and partly because I'll assume things work
until I find otherwise.

So explaining in great detail why mixing these things up isn't a good
plan seems like the best bet to make sure the message gets across -- the
KB article just says "this isn't supported", but not really why it's not
supported..

-- dan