VS 2005 c#.net shared adding project for outlook

  • Thread starter Thread starter BalajiGopalakrishnan via OfficeKB.com
  • Start date Start date
B

BalajiGopalakrishnan via OfficeKB.com

I am developing a Outlook Addin using SharedAddin project type in VS 2005(C#).
My Addin works fine in all our development machines.When I tired to create an
installer file and installs in any target machine, my installer file installs
with out any error but my addin doesnt get loaded in outlook..

Please Help me in this issue

Thanks,
Bala
 
What version of Outlook are you targeting? Please provide all relevant
information in your posts.

Office 2003 does not install the needed PIA's, that's optional. Make sure
they are there. You also need to install Extensibility.dll unless you are
targeting Outlook 2007.

You need to set the security of your assembly after signing the code with a
strong naming so it will run on the target system and make sure your users
have the correct Framework version. You also need to investigate if you need
to install KB 908002 (http://support.microsoft.com/kb/908002). Check on that
too.

One other thing. If you aren't using a shim you should do so to ensure that
your addin has its own AppDomain. If not and any other non-shimmed addin has
a problem it will end up causing all shared addins in that AppDomain
namespace to also be disabled.
 
Hi Ken,
First of all my heartly thanks for replying my message.

I am using Microsoft Outlook 2003 (11.5608.5606) in XP(Professional)
operating system. The project is developed using Visual Studio 2005(Shared
Add-in Type -- C#).The following references are included in the project.

· Microsoft Office 11.0 object library (TypeLib version 2.3)
· Microsoft Outlook 11.0 object library (TypeLib version 9.2)

In OnStartupComplete event we have written the code for creating the toolbar
and toolbar buttons.
In OnBeginShutdown event we have written the code to just to delete the
toolbar buttons.

I have added one of the prerequisites as Office 2003 PIA while creating the
setup itself.I have created the assembly and also I have signed it, but after
creating how to set the security for it?

I have checked with installing KB 908002 (
http://support.microsoft.com/kb/908002), but in vain.

Also just before replying your thread, I tried using Shim solution(
http://msdn2.microsoft.com/en-us/library/aa140200(office.10).aspx), I have
also incorporated each and every step explained in this site, but still in
vain.

I dont know where I am making the mistake.Please help me.

Thanks & Regards,
Bala.




What version of Outlook are you targeting? Please provide all relevant
information in your posts.

Office 2003 does not install the needed PIA's, that's optional. Make sure
they are there. You also need to install Extensibility.dll unless you are
targeting Outlook 2007.

You need to set the security of your assembly after signing the code with a
strong naming so it will run on the target system and make sure your users
have the correct Framework version. You also need to investigate if you need
to install KB 908002 (http://support.microsoft.com/kb/908002). Check on that
too.

One other thing. If you aren't using a shim you should do so to ensure that
your addin has its own AppDomain. If not and any other non-shimmed addin has
a problem it will end up causing all shared addins in that AppDomain
namespace to also be disabled.
I am developing a Outlook Addin using SharedAddin project type in VS
2005(C#).
Click to expand...
[quoted text clipped - 8 lines]
Thanks,
Bala
Click to expand...
Click to expand...
 
You need to do more than just reference the Outlook and Office PIA's you
need to ensure that they are on the target systems or prevent your addin
from even installing. Same for the Framework version and that KB article.

For that you need to set pre-requisites. That KB article has very specific
instructions on how to download the redistributable for the KB fix and how
to add it as a pre-requisite for your installer. I just followed the
instructions there when I create my own set of packages to install and set
of pre-requisites.

Make sure you are distributing all that stuff and checking the
pre-requisites. Also read the deployments walkthroughs on setting security,
they are pretty thorough. If you follow the instructions you should be just
fine.
 
Back
Top