the error was:
the Key in HKLM..\Outlook\AddIns was wrong: it must be the project name
followed by ".AddIn". The Key in HKCU was "automatically" correct, because it
was produced by the register process of the AddIn-DLL.

"Claus" wrote:

my msi works, if I run it under an admin accout and write the registry stuff
to HKCU.
It doesn't work (no error occures, but the addin doesn't load), neither for
the current admin user nore for other users, if I write the registry stuff to
HKLM.
Do you have any idea, what the reason could be?

thank you again,
Claus


"Ken Slovak - [MVP - Outlook]" wrote:

That would depend on whether the client wants their users to be able to
disable the addin in the COM Add-Ins dialog. If so you must register in
HKCU. That can be done by running a logon script that would run the
installer for each user when they log on to Windows if the addin wasn't
already registered. If an admin installation in HKLM it can be run once on
each computer or deployed using SMS or by a logon script.

I would never install in \System32 however, that's bad practice. I would use
a path under Program Files.

An MSI can be run by calling msiexec.exe using the switch for silent
installation if desired.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Claus" wrote in message
...
thank you, Ken,

so, how is a Outlook AddIn normaly installed for all users in a bigger
network?
the customer just said, he needs an MSI Installer.
Should an MSI setup, wich writes to HKLM and installs the AddIn-DLL to
let's
say systems32, work, so that the administrator can do the installation for
all users?