Outlook XP Add In: security problem

[Sylvain Gross]

I'm currently developing an Outlook XP Add in with .NET.
This AddIn has to
· Read some Contact in the contact folder
· Modify the recipients list of a Mail Item
· Send a Mail Item
All those operation are restricted operation, due to the "new" Outlook
Guard, against virus. So when I use my Addin, I get many MessageBox
warning, where the user is asked to confirm the operation. It's not so
practical for the user !

On internet, I found a lot of solution to avoid these warning
messages, but no one suits me:
· Use Outlook Security Form (adminpack) to "trust" my assembly, and
use a COM shim component. As far as I understand, this option is
available only with Exchange. My customer will not always being
Exchange users...
· Use an application like "Redemption" which access to Outlook
functions through low level API. It seems to be OK to read some
information (contact, recipient) but when I want to Send, I get a
error message saying that I have not the permission. In Addition, some
properties are not directly available (for example
MobileTelephoneNumber) => so I have to use both Redemption, and
MAPIProp (COM wrapper for MAPI DLL's)
· Use a ClickYes application in order to automaticly Clic on the Yes
button. This solution is not so professional. And in some case,
Outlook displays a 5 second progress bar before we can validate…

So my question is: how can I access to Contact, recipients and Send()
without warning message, and without using a makeshift job. What is
the Microsoft recommended solution ?
Thank you for your help, and sorry for this long post…

Sylvain

 

[Ken Slovak - [MVP - Outlook]]

I use Redemption myself and I know quite a few other developers that also
do. You should have no problems with reading MobileTelephoneNumber, that's
not a restricted property. Any property that isn't restricted is passed by
Redemption to the underlying Outlook or CDO item. I'm not sure about your
permissions error, I just use the .Send method on the item to submit it to
the transport mechanism and then use Redemption.MAPIUtils.DeliverNow to
actually do a send/receive.