gerwald
Posts: 3
Joined: 2015-06-17
|
Hi!
We maintain an Outlook Plugin and try to suppress Outlook security warnings with SecurityManager.
Although we disable all warnings, some security warnings still appear on some machines.
Now we have had a deeper look in this disabling process and found out, that we get the following result when disabling CDO warnings -> osmCDONotFound
Here is the code:
AddinExpress.Outlook.osmResult result = SecurityManager.Check(AddinExpress.Outlook.osmWarningKind.osmCDO);
if (result == AddinExpress.Outlook.osmResult.osmCDONotFound)
Logger.Log("Outlook Security cannot be disabled because CDO is not found");
if (result == AddinExpress.Outlook.osmResult.osmOK)
SecurityManager.DisableCDOWarnings = true;
Can you tell me what CDO warnings actually are, and why we obviously cannot disable them (since resulte is osmCDONotFound)? Also it would be nice to know what impact it has, not to disable these kinds of warnings?
Additional Information: Addin Express v9.4.4644 and SecurityManager v9.6.3406
Thank you!
Best regards |
|
Andrei Smolin
Add-in Express team
Posts: 18793
Joined: 2006-05-11
|
Hello gerwald,
You should ignore this if you do not use CDO. CDO was an older way of communicating with Outlook; now you only have MAPI and the Outlook object model.
Andrei Smolin
Add-in Express Team Leader |
|