I'm wondering if that's due to using VS Express rather than the full-blown
version. I recall something about limitations of VS Express. According to
the feature comparisons at
http://msdn2.microsoft.com/en-us/express/aa700921.aspx addins aren't
supported by VS Express, so that might be the problem.

FWIW, I've never had any problems deploying extensibility addins for Outlook
as long as the requirements were installed on the target computer. It's not
like with VSTO, which can make deployment a real chore.

If OnConnection isn't being fired it's one of 2 things:
missing prerequisites or requirements or limitations in the Express
package.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"bernat" wrote in message
...
I've deployed all dependencies on my client machine, including stdole.dll
but
the add-in doesn't load.
When I open Outlook on my client machine, the Add-in doesn't execute the
OnConnection method and changes the LoadBehavior from 3 to 2 on the
registry.
Every time I change the LoadBehavior to 3 and then execute Outlook, it
changes the property to 2.
I'm not using VSTO, instead, I've written the Add-in from scratch,
implementing Extensibility.IDTExtensibility2 and writing all registry keys
needed for the add-in to work.
Today i've been developing a simple/dummy outlook addin on the client
machine, the add-in shows a popup box when outlook starts, and it works!
but
it works only on the developing machine. If I put this simple/dummy addin
on
my original machine, it doesn't load nor run.
No matter the complexity of the add-in, for me, an outlook add-in only
runs
on the development machine.