Deploying Word Add-in

[KenWilson]

I have written a shared add-in for Word using VS 2005. I would like to
deploy the add-in so that it is installed for all users on a given machine.
I am at a loss, however, on where to direct the setup to put the files.
Currently they are all being installed to the following directory:

C:\Program Files\<Company Name>\<Application Name>

We would prefer the files be deployed properly so that the add-in becomes
available immediately no matter who is using Word which currently is not the
case when we test install the package.

The files currently being packed for installation are our .dll containing
our code and the following assemblies;

Microsoft.Office.Interop.Word.dll
Microsoft.Vbe.Interop.dll

Can anyone clarify where I should instruct the setup to put these files?

 

[Sigurd Stenersen]

I have written a shared add-in for Word using VS 2005. I would like
to deploy the add-in so that it is installed for all users on a given
machine. I am at a loss, however, on where to direct the setup to put
the files. Currently they are all being installed to the following
directory:

C:\Program Files\<Company Name>\<Application Name>

I'm not an expert on this, but I think your choice of folder is okay. The
question should be if there is a registry key that will make the plugin
available for all users, as the usual procedure is to use HKCU.

Maybe you have to add your addin to the same relative registry location for
each user under HKU.


Sigurd

 

[David Thielen]

Hi;

You are correct - you put the registry entries in HKLM instead of HKCU -
that's the only difference.

BTW - I find WIX much better for installing than the Visual Studio setup.
WIX is what Microsoft uses for it's installers (including I believe Visual
Studio).

 

[Sigurd Stenersen]

I find WIX much better for installing than the Visual Studio
setup. WIX is what Microsoft uses for it's installers (including I
believe Visual Studio).

Excellent tip - this is something I really need.

I've been using Visual Studio Installer, which is easy to use but it's way
too cumbersome with regards to upgrades.

Thanks a lot for mentioning this.


Sigurd