I am doing my testing on a Windows 7 machine with Office 2007. ![]() Is there a way for an uninstaller to clean up Per User registry entries on uninstall for a user other than the one running the uninstall? Is there anyway to stop Word from trying to load the add-in if the file does not exist? I am including "|vstolocal" at the end of the registry entry per the Registry Entries for Application-Level Add-Ins msdn article. That does not work - Word reports an error trying to "install" the customization on the next run. I was hoping this would be a problem and that Word would just ignore the missing Add-in on the next startup. My un-installer (run again by an administrator) can deal with everything that it created but does not have a way to remove the Per User registry keys. ![]() The problem I am stuck with now is how to uninstall the add-in. ![]() Then the users who actually needed the add-in would be instructed to run the utility one time and click on the "Enable" button. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |