COM add-in for Outlook not showing

[Lee]

My COM addin for OL2007(Release) always appears in list of "Inactive
application addins" of the Trust Center.

In the macro security settings I have "No security check for macros". Also
the "Apply macro security settings for installed add-ins" is checked.

LoadBehavior is set to 3 in the registry.

Thanks for any help.

 

[Ken Slovak - [MVP - Outlook]]

Is this on the development computer or a computer you deployed to?

If you go to the COM addins dialog in the Trust Center and view the addin is
it checked? What happens if you check it to enable it?

When Outlook is running what's the LoadBehavior setting in the registry, is
it still 3?

Can you run in debug mode on that computer?

What technology did you use for your addin: .NET shared addin, VSTO, what
OS, anything else that might be helpful?

If this is a .NET addin how do you deploy it: do you set security, sign the
addin, distribute PIA's and any other pre-requisites and dependencies?

 

[Lee]

Hi Thanks for the response. Here are the answers
1. This is a computer I deployed my add-in on. This is a freah VMware
template having OL2007 installed on it. (the host comp is the development
machine)
2. The LoadBehavior in registry still remains 3
3. I tried remote debugging appln from the dev computer. It doesnt hit the
break points in there.
4. Its a .NET shared addin, written in C#.
5. In Outlook the security is set to low. No the add-in is not signed.
All other dependencies are deployed.

Regards,
Lee

The add-in surprisingly loads in OL2007 beta but fails to load in release
version.

 

[cserold]

Have you tried looking at the "Disabled Items" list that is accessible via
the Help menu? I doubt this is your problem but this was an issue I was
having. The AddInLoader.dll file had been added to this list after one of my
apps threw an error. This was preventing outlook from attaching to the
Visual Studio process when debugging.

 

[Ken Slovak - [MVP - Outlook]]

Have you re-compiled with the RTM version of Outlook 2007 on the development
machine? I haven't had any problems like that moving to the release version
from the beta, although I did have to change some of my form region code due
to the addition of a couple of callbacks for form regions. Are you using any
form regions (although that shouldn't affect startup).

Can you add code to display a message box when you get OnConnection, or at
least write to a log file or something? If you're not getting that event
then of course nothing would work.

Also, I'd try setting up a new VM and seeing if you have the problem there,
or on some different machine.

One other question, is this on Vista? If so does it happen also if you
deploy to a Windows XP machine? Just for laughs, try adding strong naming
and a signature to your addin before deploying it.