RequestService override doesn't seem to be firing

[chick]

I created an Outlook 2007 add in in VS2005, and added a "Ribbon
Support" class to add a button to the ribbon on mail items. This
works just fine and dandy when I run it in VS (both in debug and
release configurations). But when I package it up in a deployment
project and do an actual install, it doesn't work (the button never
gets added to the ribbon).

I've made sure both VSTO SE runtime and the 2007 PIA's are installed.
And the addin works just fine in explorers (which use good old command
bars), so it shouldn't be a CAS policy issue. Are there any other pre-
reqs I'm not aware of for ribbon support?

The machine I'm testing deployment on is also the development machine,
so perhaps that's the issue? Does anyone have any ideas?

 

[Ken Slovak - [MVP - Outlook]]

Deploying on the development machine shouldn't be a problem. I do that on my
various development VM's.

So in the deployed addin it's running and creating the CommandBar UI for the
Explorers? Have you tried adding logging when you hit the RequestService
override to see if that code is actually entered?

I'm assuming that your override code is correct and that you have the proper
ribbon callbacks and XML for the ribbon, if things work when run from within
VS. That's a correct assumption?

Have you looked at Fusion logging at all to see if any unexpected errors are
being fired at runtime? There's a nice article on that at
http://blogs.msdn.com/vsod/archive/2008/04/22/Troubleshooting-com-add-in-load-failures.aspx.
It might help.

 

[chick]

I actually just managed to solve this issue after much playing. The
problem was with my deployment package, which was originally based off
the output from a 2003 plugin. Turns out that the settings are a
little different for a 2007 plugin and those differences are crucial
for the ribbon extensibility to work right:

1. The register property for the "primary output from {addin
project}" needs to be set to vsdrpCOMRelativePath
2. There needs to be a single "Manifest" registry entry under
HKEY_Current_User\Software\Microsoft\Office\Outlook\Addins\{addin
name}

Once I made those changes to the deployment package, it installed and
ran like a charm. Hallelujah!