|
Daniel Gustafson
Posts: 14
Joined: 2016-01-12
|
Hi Forum team, I was hoping for some help completing the deployment of my add-in express project using WIX.
This installation will need to be run for all computers and installed when built, so we will use Microsoft's SCCM to install. This seems to create a problem since the installation runs as SYSTEM. I was able to solve the first problem by changing the definition of DIRCA_TARGETDIR/TARGETDIR to reference C:\Program Files (x86)\[Manufacturer]\ProductName and the Registry to reference HKLM instead of HKCU. The result is that my add-in is installed to Program Files (x86) directory as needed.
ADXRegistrator doesn't seem to be able to register an add-in for all users (or am I missing something). I need the addin registered in HKLM\SOFTWARE\Wow6432Node\Microsoft\Office\Outlook\Addins so it can be loaded for all users (including new users of the PC) automatically.
Can someone please help point me where I'm going wrong? Below is my Registrator log file. The add-in seems to be registered to HKUsers\.DEFAULT\Software\Microsoft\office\Outlook\Addins.
I was looking at this post however I didn't understand what the end resolution for installing add in for all users on a PC. https://www.add-in-express.com/forum/read.php?FID=5&TID=8400&MID=42563#message42563
Add-in Express Registrator Log File: 02/01/2016 17:31:03
Installation directory: C:\WINDOWS\Installer\
Registrator version: 8.0.4330.0
Operating System: Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit
Process Owner: System
Command Line: "C:\WINDOWS\Installer\MSI1354.tmp" /install="C:\Program Files (x86)\BlueMountain Capital management\BM_OLSec\BM_OLSec.dll" /privileges=user
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: System
UAC (User Account Control): On
--------------------------------------------------------------
17:31:03 0192 Starting the add-in registration process.
17:31:03 0192 Loading mscoree.dll
17:31:03 0192 Success.
17:31:03 0192 .NET Framework installation directory:
17:31:03 0192 The latest version of .NET Framework: 'v4.0.30319'
17:31:03 0192 Loading CLR: v4.0.30319.
17:31:03 0192 Calling CLRCreateInstance method.
17:31:03 0192 Success.
17:31:03 0192 Calling GetRuntime method.
17:31:03 0192 Success.
17:31:03 0192 Checking if the hosting API of .NET Framework v4.0 beta is installed.
17:31:03 0192 The hosting API is up to date.
17:31:03 0192 Calling GetInterface method for the CorRuntimeHost interface.
17:31:03 0192 Success.
17:31:03 0192 Starting CLR...
17:31:03 0192 Success.
17:31:03 0192 Getting the CLR version.
17:31:03 0192 The CLR v4.0.30319 has been initialized successfully.
17:31:03 0192 Creating a new domain setup.
17:31:03 0192 Success.
17:31:03 0192 The 'shadow copy' is disabled.
17:31:03 0192 Creating a new application domain.
17:31:03 0192 Success.
17:31:03 0192 Getting the base directory for the domain.
17:31:03 0192 Success. The directory is 'C:\Program Files (x86)\BlueMountain Capital management\BM_OLSec\'.
17:31:03 0192 Searching for the Add-in Express core library.
17:31:03 0192 Success. The 'AddinExpress.MSO.2005.dll' file is found.
17:31:03 0192 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
17:31:03 0192 Assembly identity is 'AddinExpress.MSO.2005'.
17:31:03 0192 Success.
17:31:03 0192 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
17:31:03 0192 Success.
17:31:03 0192 Calling the managed registration procedure (DISPID = 1610743823).
17:31:03 0192 Success.
17:31:03 0192 The add-in registration process is completed with HRESULT = 0. |
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Hello Daniel,
You need to follow the steps listed in section Deploying a per-machine Office extension via an MSI installer, see the PDF file in the folder {Add-in Express}\Docs on your development PC.
Andrei Smolin
Add-in Express Team Leader |
|
|
Daniel Gustafson
Posts: 14
Joined: 2016-01-12
|
Andrei - Thank you. I must have somehow glossed over a few steps in the document. I believe the key point I was missing was the Post-Build action and Unregistering the add-in before generating the setup project.
I was able to deploy my add-in using SCCM with the command line "setup.exe /qn".
I really appreciate the usefulness of the forums! |
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Hello Daniel,
No problem and thanks!
Andrei Smolin
Add-in Express Team Leader |
|
Forums
Topics
Search
Help
Login
Register