culminIT
asked on
VSTO add-in works in all Office apps except Outlook
Hi
I am currently working on creating an add-in for Outlook 2010. I am using VS.NET 2010 and chose the Outlook 2010 add-in.
I proceeded to add a ribbon control and added the tab with a couple of buttons. When debugging the tab does not show at all.
I did exactly the same for a Word add-in and it showed immediately after Word loaded.
Am I missing an option somewhere in Outlook? Is this a known issue?
Please advise me on possible ways to fix this.
Thank you
I am currently working on creating an add-in for Outlook 2010. I am using VS.NET 2010 and chose the Outlook 2010 add-in.
I proceeded to add a ribbon control and added the tab with a couple of buttons. When debugging the tab does not show at all.
I did exactly the same for a Word add-in and it showed immediately after Word loaded.
Am I missing an option somewhere in Outlook? Is this a known issue?
Please advise me on possible ways to fix this.
Thank you
ASKER
Hi
Sorry for the delay. All of these things seem to be in place. There are no alerts either when I start up outlook (if I am doing it correctly). The add-in is loaded into outlook. I have checked that as well.
This is rather strange behaviour seeing as it even works in debug mode with a word add-in, but not outlook. I have tested this is on two different machines that use Outlook 2010.
Any other ideas on what the issue might be?
Thank you
Sorry for the delay. All of these things seem to be in place. There are no alerts either when I start up outlook (if I am doing it correctly). The add-in is loaded into outlook. I have checked that as well.
This is rather strange behaviour seeing as it even works in debug mode with a word add-in, but not outlook. I have tested this is on two different machines that use Outlook 2010.
Any other ideas on what the issue might be?
Thank you
Did VSTO_LOGALERTS = 1 not create a log file in your add-in folder ?
Are you able to put trace statements or even message boxes in various points in your add-in startup code to see how far it gets ? does it even get to the startup or not ?
Are you catching exceptions in the startup code ? I would wrap it with a try/ catch and see if it throws any problems
ASKER
The custom ribbon tab is supposed to show up without you having to d anything in the startup code. All of the examples I have seen do it in this manner. I also did it like this and it works, just not for outlook.
It did not create the log file no. When starting up outlook, it even shows that the add-in is being loaded (on the splash screen)
I set the variable to VSTO_LOGALERTS and the value to 1. Is this correct?
Thanks
It did not create the log file no. When starting up outlook, it even shows that the add-in is being loaded (on the splash screen)
I set the variable to VSTO_LOGALERTS and the value to 1. Is this correct?
Thanks
OK I cant tell what else could be going wrong. If you can upload your project I will be happy to take a look for you
ASKER
Hi
Here is the example. Hope it works. I had to cut out a couple of files due very restrictive rules for file uploading.
Thank you
OutlookAddIn1.zip
Here is the example. Hope it works. I had to cut out a couple of files due very restrictive rules for file uploading.
Thank you
OutlookAddIn1.zip
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
Also check if the registry key LoadBehaviour is set to anything other than "3", is fo, change it back to "3"
the key is under HKEY_CurrentUser\Software\
I have also found that you need to close down Outlook completely before it will pick up any new addins - check that you dont have OUTLOOK.EXE running in the Processes tab in Task Manager
If nothing works, you can add trace statements in your add-in startup code to see how far it gets
Setting Environment Variables :-
Go to Control Panel / System / Advanced / Environment Variables / System Variables section
Add New
VSTO_LOGALERTS = 1
this will add to a log file in the add-in install folder (manifest file name .log)
Add New
VSTO_SUPPRESSDISPLAYALERTS
this will display the problem on the screen