whither cdo?

bit of a heads-up, so you might want to pay attention, kiddos...

starting with the 2007 versions of outlook and exchange server, the mothership is totally separating collaboration data objects aka cdo, and making this particular component a separate download.

the reason for the heads-up?

this directly affects a veritable smorgasbord of 3rd party apps.

cdo is basically an application programming interface aka api that enables access to mapi stores and certain objects therein.

the first thing that immediately jumped to mind when i saw this come across the download center?

that's right...

our old pal...

blackberry enterprise server

bes relies on cdo to work its mojo with exchange server.

in fact...

the reason bes has such an insane amount of prerequisite prep time lies in the absolute criticality of getting the cdo environment squared away.

is this yet another way for ms to exert indirect pressure on competing products like blackberry?

i'll leave that for the folks who get comped steak dinners to declare.

main thing to take from this is...

from here on out...

cdo is an extra step.

and if you've got a mail-enabled app...

you prolly need to check the readme, errata, or install notes pretty closely to see if it needs cdo...

before you find yourself hip-deep in a hosed install.

consider yourself warned...