Hi gang,
We have a custom IExtensibility2-based Outlook AddIn that runs in Outlook 2003, 2007, and 2010 (i.e. we're not using VSTO). In most cases, the AddIn loads and runs fine, but if the user turns on the "Apply macro security settings to installed add-ins" setting (via Tools->Trust Center->Add-ins), then our AddIn is silently not loaded.
When you turn this setting on and restart Outlook, the user is prompted to allow/reject any AddIns for which the signing cert is not in the trusted source list... except ours. The user is never given the opportunity to add us to the trusted source list.
If you go into the Trust Center, and click on the "Manage: -> Go..." button on the Add-ins page, then find our AddIn in the list, the "Load Behavior" info is:
"Not loaded. Certificate of signed and load at startup COM Add-in is not in trusted source list"
I have a self-contained VS2010 solution/project in a 1.5MBish zipfile if anyone is interested in having a go at the problem. The prereqs are:
- You have Outlook 2003, 2007, or 2010 installed
- You have VS2010 installed
- You have a "known good" code signing cert for experimentation with various signing options
- Very strong hair roots so your hair stays in after a good amount of pulling.. ;-)
If I can figure out how to submit the sample project here, I will do so, otherwise I can send you the zipfile.
Thanks in advance for any help... this one's really got me stumped.
Tyler