Charles Lam
Posts: 7
Joined: 2025-02-21
|
Hello All,
Backstory Start
We have an old Addin Build with add-in-express (sadly the developer is no more availiable), and as far as I know the plugin was "deployed" with some commands / powershell scripts. This seems to work and on updates we just had to replace the dll.
Currently there seems to be an issue and this only works with PC's where the plugin was already installed, with new clean installs the this doesn't work. And currently I can't find out what the developer did, or if he had some special scripts on his dev-machine.
Backstory End
Now to my questions is it somehow possible to install a plugin without using a installer? Is copying the files and registiering the dlls enough? I tried out some stuff I found in the Forums, but nothing worked.
I tinktered with the manifest, the adxregistration, regsvr32, ...
Even the adxloader.log - File looks okay
Add-in Express Loader Log File: 02/21/2025 09:04:25:996
Startup directory: C:\Programme_x64\Fabasoft\Outlook2Faba\
Loader version: 10.2.4714.0
Operating System: Microsoft Windows 10 Enterprise Edition (build 19045), 64-bit
Process Owner: Administrator
Command Line: "C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE"
Run 'As Administrator': No
Process Elevated: No
Integrity Level: Medium
UAC (User Account Control): On
------------------------------------------------------------------------
09:04:25:997 7444 17256 Starting the add-in registration process.
09:04:25:997 7444 17256 Loading mscoree.dll
09:04:25:997 7444 17256 INFO: Assembly codebase - C:\Programme_x64\Fabasoft\Outlook2Faba\FabaOutlook2010Plugin.dll.
09:04:25:997 7444 17256 INFO: Assembly version - 24.10.4.1.
09:04:25:997 7444 17256 Getting the latest CLR version.
09:04:25:997 7444 17256 The latest CLR version is 'v4.0.30319'.
09:04:25:997 7444 17256 Loading CLR: v4.0.30319.
09:04:25:997 7444 17256 Calling CLRCreateInstance method.
09:04:25:997 7444 17256 Success.
09:04:25:997 7444 17256 Calling GetRuntime method.
09:04:25:997 7444 17256 Success.
09:04:25:997 7444 17256 Checking if the hosting API of .NET Framework v4.0 beta is installed.
09:04:26:002 7444 17256 The hosting API is up to date.
09:04:26:002 7444 17256 Calling SetDefaultStartupFlags method.
09:04:26:002 7444 17256 Success.
09:04:26:002 7444 17256 Calling GetInterface method for the CorRuntimeHost interface.
09:04:26:002 7444 17256 Success.
09:04:26:002 7444 17256 Starting CLR...
09:04:26:002 7444 17256 Success.
09:04:26:002 7444 17256 Getting the CLR version.
09:04:26:002 7444 17256 The CLR v4.0.30319 has been initialized successfully.
09:04:26:002 7444 17256 Creating a new domain setup.
09:04:26:003 7444 17256 Success.
09:04:26:003 7444 17256 Getting the add-in directory.
09:04:26:003 7444 17256 Success. The directory is 'C:\Programme_x64\Fabasoft\Outlook2Faba\'
09:04:26:003 7444 17256 The configuration file is 'C:\Programme_x64\Fabasoft\Outlook2Faba\FabaOutlook2010Plugin.dll.config'
09:04:26:003 7444 17256 The 'shadow copy' is disabled.
09:04:26:003 7444 17256 Creating a new application domain.
09:04:26:004 7444 17256 Success.
09:04:26:004 7444 17256 Getting the base directory for the domain.
09:04:26:005 7444 17256 Success. The directory is 'C:\Programme_x64\Fabasoft\Outlook2Faba\'.
09:04:26:005 7444 17256 Searching for the Add-in Express core library.
09:04:26:005 7444 17256 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
09:04:26:005 7444 17256 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
09:04:26:005 7444 17256 Assembly identity is 'AddinExpress.MSO.2005'.
09:04:26:009 7444 17256 Success.
09:04:26:009 7444 17256 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
09:04:26:010 7444 17256 Success.
09:04:26:010 7444 17256 Creating an instance of the XML parser class.
09:04:26:010 7444 17256 Success.
09:04:26:010 7444 17256 Loading the manifest file (C:\Programme_x64\Fabasoft\Outlook2Faba\adxloader.dll.manifest).
09:04:26:010 7444 17256 Success.
09:04:26:010 7444 17256 Getting the root element of the manifest (C:\Programme_x64\Fabasoft\Outlook2Faba\adxloader.dll.manifest).
09:04:26:010 7444 17256 Success.
09:04:26:010 7444 17256 Getting the 'assemblyIdentity' element of the manifest (C:\Programme_x64\Fabasoft\Outlook2Faba\adxloader.dll.manifest).
09:04:26:010 7444 17256 Success.
09:04:26:010 7444 17256 Searching for the 'name' attribute of the 'assemblyIdentity' element.
09:04:26:010 7444 17256 Success. The name is 'FabaOutlook2010Plugin, PublicKeyToken=81e387c94cfe7d60'.
09:04:26:010 7444 17256 Calling the managed procedure to register the 'FabaOutlook2010Plugin, PublicKeyToken=81e387c94cfe7d60' assembly.
09:04:26 19476 17256 Connecting to the application domain of the Add-in Express loader.
09:04:26 19476 17256 Success.
09:04:26 19476 17256 Loading the 'FabaOutlook2010Plugin, PublicKeyToken=81e387c94cfe7d60' assembly.
09:04:26 19476 17256 Success.
09:04:26 19476 17256 Registering the 'FabaOutlook2010Plugin, PublicKeyToken=81e387c94cfe7d60' assembly (user).
09:04:26 19476 17256 The ' FabaOutlook2010Plugin, PublicKeyToken=81e387c94cfe7d60' assembly has been registered successfully.
09:04:26 19476 17256 The managed registration process is complete with HRESULT = 0.
09:04:26:058 7444 17256 The add-in registration process is completed with HRESULT = 0.
What would have to be the concret steps to install a plugin? Am I missing something?
Any tipps are pointers are very welcome.
Kind Regards
Charles |
|
Andrei Smolin
Add-in Express team
Posts: 19095
Joined: 2006-05-11
|
Hello Charles,
Using an installer is a preferred way: without it, you should be ready to fall in multiple traps that the installer foresees.
A simple way is to run adxregistrator.exe: see custom actions in sections
- Deploying a per-user Office extension via an MSI installer.
- Deploying a per-machine Office extension via an MSI installer.
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
Charles Lam
Posts: 7
Joined: 2025-02-21
|
Hello Andrei,
Thanks again for your fast response, I had tried the suggest pointer already, but they never worked. But since I just now tested the code with a "normal" msi install, and it doesn't work (debugging also stopped working). I assume the issue I have, is in the plugin application itself. I think I will have to reset and start with a small demo Project, to pinpoint the real issue.
In anycase thanks for your support.
Kind Regards
Charles |
|