VSTO 2005 SE runtime + Office 2007 PIA: private assemblies vs shared assemblies

[Ojas]

For our VSTO 2005 SE plug-in for Outlook 2007, we know the exact
assemblies we need from the VSTO 2005 SE runtime and the Office 2007
PIA.

What are the pros and cons of us using our own installer to install
these shared assemblies as private assemblies in the same application
directory as our plug-in?

If we use Microsoft's installers and install the assemblies as "shared
assemblies", if another third party product installs a newer version
of either the VSTO 2005 SE runtime or the Office 2007 PIA, could that
impact our plug-in? I would think that assembly versioning would take
care of that.

The argument being made is that if we use our private assemblies for
the files we need from the VSTO 2005 SE and Outlook 2007 PIA
installers then we will not have to worry about versioning issues if
other products install newer versions of these assemblies.

[Ken Slovak - [MVP - Outlook]]

The official position that I'm familiar with is that if it's an official PIA
then it should be installed in the GAC. Of course you can do whatever you
want, but that's the way it's supposed to be. Installation of a later
version in the GAC is supposed to preserve COM compatibility.
--
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

Post by Ojas
For our VSTO 2005 SE plug-in for Outlook 2007, we know the exact
assemblies we need from the VSTO 2005 SE runtime and the Office 2007
PIA.
What are the pros and cons of us using our own installer to install
these shared assemblies as private assemblies in the same application
directory as our plug-in?
If we use Microsoft's installers and install the assemblies as "shared
assemblies", if another third party product installs a newer version
of either the VSTO 2005 SE runtime or the Office 2007 PIA, could that
impact our plug-in? I would think that assembly versioning would take
care of that.
The argument being made is that if we use our private assemblies for
the files we need from the VSTO 2005 SE and Outlook 2007 PIA
installers then we will not have to worry about versioning issues if
other products install newer versions of these assemblies.