B
BeanDog
I did the following:
Create a new Extensibility->Shared Add-in project in Visual Studio 2005
Standard
Select C# and only Outlook.
Check both boxes "I would like my add-in to load when the host application
loads" and "My Add-in should be available to all users."
Modify Connect::Connect() to have a call to MessageBox.Show("Test");
Build the project and open Outlook (the message box shows correctly).
Build the deployment project and install on another machine with Office 2003
Pro.
For good measure (even though Outlook was installed with all options),
install the Office 2003 PIA.
Open Outlook and see that no messagebox appears.
What have I done wrong? What can I do to get my plugin to work on a machine
other than my development machine? I currently get no errors or notification
from Outlook that something has gone wrong; the add-in simply fails to load.
The deployment project seems to have created the appropriate registry
entries in HKLM/Software/Microsoft/Office/Outlook/Addins. And it seems to be
actively using those keys, too--I changed LoadBehavior on my addin to 3 (load
on startup | currently loaded), and after running Outlook I see it's been
changed to 2 (load on startup | not loaded).
Any clues?
Ben Dilts
Create a new Extensibility->Shared Add-in project in Visual Studio 2005
Standard
Select C# and only Outlook.
Check both boxes "I would like my add-in to load when the host application
loads" and "My Add-in should be available to all users."
Modify Connect::Connect() to have a call to MessageBox.Show("Test");
Build the project and open Outlook (the message box shows correctly).
Build the deployment project and install on another machine with Office 2003
Pro.
For good measure (even though Outlook was installed with all options),
install the Office 2003 PIA.
Open Outlook and see that no messagebox appears.
What have I done wrong? What can I do to get my plugin to work on a machine
other than my development machine? I currently get no errors or notification
from Outlook that something has gone wrong; the add-in simply fails to load.
The deployment project seems to have created the appropriate registry
entries in HKLM/Software/Microsoft/Office/Outlook/Addins. And it seems to be
actively using those keys, too--I changed LoadBehavior on my addin to 3 (load
on startup | currently loaded), and after running Outlook I see it's been
changed to 2 (load on startup | not loaded).
Any clues?
Ben Dilts