![]() Installing per-machine will require admin privileges from your users (maybe not all will have that privileges) and you will also have to work much more to see where to write the registry entries under HKLM, because here you have the key " Wow6432Node" dedicated to 32 bit applications, so based on the edition of WIndows and that of Office you need to see if you will need to write under " HKLM\Software\Office." or under " HKLM\Sofware\Wow6432Node\Office.". I recommend installing the addin per user, that is to install the files under APPDATA folder and the registry entries under HKCU. ![]() When using a MSI to deploy the addin you basically copy your add-in resources/files in the desired installation folder and create the registry entries as mentioned by Patrick. So you can easily have your clients deploy it through Active Directory/GPO or SCCM if they need to. ![]() I would recommend to create an MSI for deploying your add-in, this is the most used distribution system from Windows, that has built-in support for silent installation, repair, rollback and uninstall.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |