Load add-in on Outlook 2003 startup

[Ken Slovak - [MVP - Outlook]]

If you positively know that CDO is installed of course you don't need to
check for it being installed.

The old InstallFeature trick worked as long as the user was working with
Office 2003 or earlier because the CDO.DLL library was on the Office CDs.
With Office 2007 CDO is no longer on the CDs but instead has to be
downloaded from the MS Web site.

CDO is being deprecated, it most likely will not be supported in the next
version of Office (Office 14). That's just a guess, but if they come out
with native 64-bit versions of Office as now planned then no 32-bit addin
will work with 64-bit versions of Office and the old 32-bit CDO won't work.
Since CDO hasn't been developed in years other than security changes and
signature changes for new Outlook versions I seriously doubt that a 64-bit
CDO will ever be produced.

Now is the time to start moving code away from CDO to alternatives, if you
haven't already begun doing so.

 

[goran]

Thanks Ken. Since this is a 2007 Outlook and CDO doesn't come with Office
2007 I will make sure Cdo is installed on user PC before I install Add-In.
What exactly do I need Cdo for? Is this to avoid Outlook security warning? I
don't use contacts at all. I just set value to a custom Mapi property from
this add-in. Can I chose not to install CDO at all?
Thanks,

Goran

 

[Ken Slovak - [MVP - Outlook]]

How would I know what you need CDO for? Are you using it at all? If not you
don't need it.

CDO is even more security restricted than the Outlook object model.

 

[goran]

Thanks.

How would I know what you need CDO for? Are you using it at all? If not you
don't need it.

CDO is even more security restricted than the Outlook object model.