S
Scott McBurney
We have customers experiencing what appears to be a bug in Outlook XP (and I
believe 2003).
We have a COM Addin, but we register it under HKEY_LOCAL_MACHINE instead of
HKEY_CURRENT_USER - that way all users of a machine get the addin, and they
cannot remove it.
Anyway, when some users come in in the morning, they log into their
machines, and put their pocket pc onto its cradle to sync. This apparently
starts the Outlook object model, but no Outlook user interface.
Then at some point later, they start Outlook from the Icon on their desktop
or a menu item.
When starting this way, our addin is never loaded and never recieves any of
the IDTEXTENSIBILITY2 events. The only way to get the addin running is to
shut down outlook, disconnect the Pocket PC, and then start outlook again.
This time our addin starts up just fine.
Any suggestions how to cure this? Is this a known issue with outlook? Its
very easy to reproduce.
believe 2003).
We have a COM Addin, but we register it under HKEY_LOCAL_MACHINE instead of
HKEY_CURRENT_USER - that way all users of a machine get the addin, and they
cannot remove it.
Anyway, when some users come in in the morning, they log into their
machines, and put their pocket pc onto its cradle to sync. This apparently
starts the Outlook object model, but no Outlook user interface.
Then at some point later, they start Outlook from the Icon on their desktop
or a menu item.
When starting this way, our addin is never loaded and never recieves any of
the IDTEXTENSIBILITY2 events. The only way to get the addin running is to
shut down outlook, disconnect the Pocket PC, and then start outlook again.
This time our addin starts up just fine.
Any suggestions how to cure this? Is this a known issue with outlook? Its
very easy to reproduce.