How to deploy Outlook Shared add-in

[Gokul]

Hi,

I created shared add-in for Outlook using visual studio 2005 and language is
vb.net. The setup file is working fine in my machine but it is not working in
another machine. When I check trust center add-in is in disable items. I am
not able to enable.

I am totally new to this. I am not able to find solution. I need setps to
create deployment setup file. Can any one help me on this.

I have asked this questions in two of similar forums but I did not find any
proper solutions. Please help me to solve this problem.

Thanks & Regards
Gokul

 

[Ken Slovak - [MVP - Outlook]]

What version of Outlook was used on the development machine?

What versions are you deploying to and supporting?

Are you shimming your addin? Are you strong naming your addin? Do you have a
manifest file? What sort of installer are you using? Are you deploying all
dependencies and requirements? Is the Framework of the correct version
installed where it's failing? Are the PIA's installed?

You need to answer all these questions and provide all the relevant
information if you want help.

First thing I'd recommend is to review the troubleshooting information for
managed code addins at
http://blogs.msdn.com/vsod/archive/2008/04/22/Troubleshooting-com-add-in-load-failures.aspx.
I've found it very useful for troubleshooting load problems, especially the
Fusion logging.

 

[Gokul]

Dear Ken,

Thanks for your reply.

What version of Outlook was used on the development machine?
Outlook 2007

What versions are you deploying to and supporting?
Outlook 2003 and 2007

Are you shimming your addin? Are you strong naming your addin? Do you have a
manifest file? What sort of installer are you using? Are you deploying all
dependencies and requirements? Is the Framework of the correct version
installed where it's failing? Are the PIA's installed?
I am totally new to this. I have read about the above, and I am not clear
with that. It is possible give me tutorial links it would help me.

Also whether any books available to read about developing and deploying for
shared add-in.

Thanks
Gokul

 

[Ken Slovak - [MVP - Outlook]]

OK, first basic thing is that you develop on a machine that has the oldest
version of Outlook installed on it that you intend to support. So you'd need
a machine with Outlook 2003 installed on it to support Outlook 2003 and 2007
(and soon 2010).

The other questions I asked are so basic that you really need to start at
the beginning. I don't know of any specific books on shared addins but you
can get some basics on that either from my book or Randy Byrne's book on
Outlook 2007 programming. You can also read some of the development articles
at MSDN. I'll list some that are useful.

Shimming, Shim Wizard: http://msdn.microsoft.com/en-us/library/bb508939.aspx

Deploying PIA's in a setup project:
http://blog.developers.ie/CGreen/archive/2006/10/27/2427.aspx

Deployment (specific for VSTO but useful anyway):
http://msdn.microsoft.com/en-us/library/aa537173(office.11).aspx

I'd also go to www.outlookcode.com and review all the information there on
COM addins, there are lots of articles and references there.

 

[Gokul]

Dear Ken,

Thanks for your reply. I read the links, sorry learned from the links.

Now I have new problem. I changed the Outlook version 2003 in development
machine, it is perfect in my machine. I tried to install on another machine
XP and Outlook 2007. God saved me, from the problem for a while. But it is
not happen for long. I extend my testing, I tried in Windows Vista and
Outlook 2007. Nothing happens, I found my add-in in inactive
application(unloaded). For me It is like treasure hunt. Also tried to change
regedit path but nothing happens. I need your help on this.

Thanks
Gokul

 

[Ken Slovak - [MVP - Outlook]]

If an addin is in the inactive list it's almost always the deployment
machine missing a dependency. It can also be a dll that needs to be
registered and isn't. Usually you use an error log to see if the code is
actually being executed before some exception caused the addin to fail. If
the addin never gets to the error log then it's usually a load failure,
again due to a missing piece.

If that's the case you need to use Fusion logging to see where things are
failing. Fusion is the managed code loader. Take a look at
http://blogs.msdn.com/vsod/archive/2008/04/22/Troubleshooting-com-add-in-load-failures.aspx,
which has invaluable information for troubleshooting managed code loading
problems, including Fusion logging.

 

[Gokul]

I got an issue like this "System.IO.FileNotFoundException: Could not load
file or assembly 'Interop.Microsoft.Office.Core" I could not proceed further.
Can some one help.

 

[Ken Slovak - [MVP - Outlook]]

That sounds like the Office and possibly the Outlook PIA's aren't installed
in the GAC. Do you set a project prerequisite for that?