
The administrator would install the add-in dll and my utility to c:\program files*.

The utility would create the correct Per User registry keys to enable the add-in. In addition, my users are only a small percentage of the users on these servers.įor those reasons I was planning on building a small utility that would ship with the Add-In. I am in a situation where an administrator will be running my install on the server as the users do not have the correct rights. A number of my users are running under Citrix or Terminal Services.

It can be per user under HKEY_CURRENT_USER or per machine HKEY_LOCAL_MACHINE.

There are some different options for installing the Add-In registry entries. I am working on deploying my first Visual Studio Tools for Office (VSTO) add-in using VSTO 4.
