add-in not getting called with EE_CONTEXT_VIEWER context ?

[Beiley]

I have occasionally had reports from users that my add-in doesn't load.
They can make it load by just going to look at the add-ins under
"Tools / Options / Other / Advanced Options... / Add-in Manager", and
not even making any changes. It seems just bringing up these dialogs
causes it to load. This doesn't happen for me on any of my test
systems, but I've had more than one user report this problem. I was
able to debug it on one of these problematic systems, and the add-in
gets loaded for these contexts:

EE_CONTEXT_TASK
EE_CONTEXT_SESSION

but then not for:

EE_CONTEXT_VIEWER

On my system where the add-in loads properly I always get loaded for
all three:

EE_CONTEXT_TASK
EE_CONTEXT_SESSION
EE_CONTEXT_VIEWER

I'm adding my menu items only when my add-in gets loaded in the
EE_CONTEXT_VIEWER context. I'm wondering if anyone has any ideas why
some systems don't seem to load the add-in in this context?

FYI, my add-in is based off of this article:

http://www.codeproject.com/useritems/Outlook-addin.asp

Thanks,
Mark Beiley
http://www.email-announcer.com

 

[Dmitry Streblechenko]

Do you install the ECE using registry or an ECF file? ECEs installed using
registry are only loaded in the viewer context for the IPM.Note messages. If
you need to support other message types, use an ECF file and specify
MoreContexts in it.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

 

[Mark Beiley]

I do use the registry for installation. I am only interested in message
views. The add-in works fine on all systems I've had direct access to, it
only affects a small percentage for some unknown reason... Any more ideas,
or thoughts on how I could debug it?

Thanks,
Mark
http://www.email-announcer.com

 

[Dmitry Streblechenko]

Are you sure the message has the IPM.Note class?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

 

[Mark Beiley]

I was able to fix this, although I don't quite understand why... Maybe it
will make sense to someone else?

My add-in is using the registry to tell Outlook what contexts to load in. I
was using:

4.0;C:\PROGRA~1\EANNOU~1\EANNOU~1.DLL;1;11000000000001;0000000

as I mentioned this worked (my add-in got loaded in the EE_CONTEXT_VIEWER
context) on all my test systems, but I had several customers report it
wouldn't load. I was able to get help debugging this from one of these
customers, and eventually determined that if we set it to load in all
contexts:

4.0;C:\PROGRA~1\EANNOU~1\EANNOU~1.DLL;1;11111111111111;1111111

that it begain loading fine on their machine. Why is this? I was cutting
back on telling it what contexts to load in, just to reduce overhead.

Thanks,
Mark
http://www.email-announcer.com