Outlook Plugin not showing up

Add-in Express™ Support Service
That's what is more important than anything else

Outlook Plugin not showing up
A create Plugin on update stopped working 
Subscribe
Charles Lam




Posts: 7
 Joined: 2025-02-21
Hello dear addinExpress Team

I'm pretty new to addinExpress, and I had take over an old plugin, and I ran into some Problems. In new small Demo Addin I build everything works fine, but I made some change to the old plugin and it doesn't load any more. (And when I select the adxloader64.dll in Outlook to add it manually it just, doesn't appear in following selection dialog ) I cnat run the plugin from the debugger, or with the installer (I added to the Project, since it didn't have one). I found some post similar to to my debugger issue, but following them didn't work for me. So I have 2 questions:

1) can I some how reset my system fast and easy so that debugging the plugin works again? (I unistalled, unregistered, delete some regkeys, ... but nothing) Something like removing specific Regisitry entries, or ...

2) how can I get my Installer to work? As far As I can see the logs look good, but I'm beginner:
The adxloader.log looks like this:

Add-in Express Loader Log File: 03/04/2025 08:51:39:244 

Startup directory: C:Programme_x64MyApp
Loader version: 10.2.4714.0
Operating System: Microsoft Windows 10 Enterprise Edition (build 26100), 64-bit
Process Owner: Administrator
Command Line: "C:Program FilesMicrosoft Office
ootOffice16OUTLOOK.EXE" 
Run 'As Administrator': No
Process Elevated: No
Integrity Level: Medium
UAC (User Account Control): On
------------------------------------------------------------------------
08:51:39:248 19976 17820 Starting the add-in registration process.
08:51:39:248 19976 17820 Loading mscoree.dll
08:51:39:249 19976 17820 INFO: Assembly codebase - C:Programme_x64MyAppMyApp.dll.
08:51:39:249 19976 17820 INFO: Assembly version - 24.10.4.1.
08:51:39:249 19976 17820 Getting the latest CLR version.
08:51:39:249 19976 17820 The latest CLR version is 'v4.0.30319'.
08:51:39:249 19976 17820 Loading CLR: v4.0.30319.
08:51:39:249 19976 17820 Calling CLRCreateInstance method.
08:51:39:249 19976 17820 Success.
08:51:39:249 19976 17820 Calling GetRuntime method.
08:51:39:249 19976 17820 Success.
08:51:39:249 19976 17820 Checking if the hosting API of .NET Framework v4.0 beta is installed.
08:51:39:249 19976 17820 The hosting API is up to date.
08:51:39:249 19976 17820 Calling SetDefaultStartupFlags method.
08:51:39:249 19976 17820 Success.
08:51:39:249 19976 17820 Calling GetInterface method for the CorRuntimeHost interface.
08:51:39:249 19976 17820 Success.
08:51:39:249 19976 17820 Starting CLR...
08:51:39:249 19976 17820 Success.
08:51:39:249 19976 17820 Getting the CLR version.
08:51:39:249 19976 17820 The CLR v4.0.30319 has been initialized successfully.
08:51:39:249 19976 17820 Creating a new domain setup.
08:51:39:249 19976 17820 Success.
08:51:39:249 19976 17820 Getting the add-in directory.
08:51:39:249 19976 17820 Success. The directory is 'C:Programme_x64MyApp'
08:51:39:249 19976 17820 The 'shadow copy' is disabled.
08:51:39:249 19976 17820 Creating a new application domain.
08:51:39:249 19976 17820 Success.
08:51:39:249 19976 17820 Getting the base directory for the domain.
08:51:39:249 19976 17820 Success. The directory is 'C:Programme_x64MyApp'.
08:51:39:249 19976 17820 Searching for the Add-in Express core library.
08:51:39:249 19976 17820 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
08:51:39:249 19976 17820 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
08:51:39:249 19976 17820 Assembly identity is 'AddinExpress.MSO.2005'.
08:51:39:257 19976 17820 Success.
08:51:39:257 19976 17820 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
08:51:39:257 19976 17820 Success.
08:51:39:257 19976 17820 Creating an instance of the XML parser class.
08:51:39:257 19976 17820 Success.
08:51:39:257 19976 17820 Loading the manifest file (C:Programme_x64MyAppdxloader.dll.manifest).
08:51:39:257 19976 17820 Success.
08:51:39:257 19976 17820 Getting the root element of the manifest (C:Programme_x64MyAppdxloader.dll.manifest).
08:51:39:257 19976 17820 Success.
08:51:39:257 19976 17820 Getting the 'assemblyIdentity' element of the manifest (C:Programme_x64MyAppdxloader.dll.manifest).
08:51:39:257 19976 17820 Success.
08:51:39:257 19976 17820 Searching for the 'name' attribute of the 'assemblyIdentity' element.
08:51:39:257 19976 17820 Success. The name is 'MyApp, PublicKeyToken=xxxxxxxxxxxxxxxxx'.
08:51:39:257 19976 17820 Calling the managed procedure to register the 'MyApp, PublicKeyToken=xxxxxxxxxxxxxxxxx' assembly.
08:51:39 23372 17820 Connecting to the application domain of the Add-in Express loader.
08:51:39 23372 17820 Success.
08:51:39 23372 17820 Loading the 'MyApp, PublicKeyToken=xxxxxxxxxxxxxxxxx' assembly.
08:51:39 23372 17820 Success.
08:51:39 23372 17820 Registering the 'MyApp, PublicKeyToken=xxxxxxxxxxxxxxxxx' assembly (administrator).
08:51:39 23372 17820 The ' MyApp, PublicKeyToken=xxxxxxxxxxxxxxxxx' assembly has been registered successfully.
08:51:39 23372 17820 The managed registration process is complete with HRESULT = 0.
08:51:39:339 19976 17820 The add-in registration process is completed with HRESULT = 0.



and the adxregistrator.log, looks like this: 

Add-in Express Registrator Log File: 03/04/2025 08:38:42

Installation directory: C:Programme_x64MyApp
Registrator version: 10.2.4714.0
Operating System: Microsoft Windows 10 Enterprise Edition (build 26100), 64-bit
Process Owner: Administrator
Command Line: "C:Programme_x64MyAppdxregistrator.exe" /install="MyApp.dll" /privileges=user
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): On
--------------------------------------------------------------
08:38:42 0512 Starting the add-in registration process.
08:38:42 0512 Loading mscoree.dll
08:38:42 0512 Success.
08:38:42 0512 .NET Framework installation directory: 
08:38:42 0512 The latest version of .NET Framework: 'v4.0.30319'
08:38:42 0512 Loading CLR: v4.0.30319.
08:38:42 0512 Calling CLRCreateInstance method.
08:38:42 0512 Success.
08:38:42 0512 Calling GetRuntime method.
08:38:42 0512 Success.
08:38:42 0512 Checking if the hosting API of .NET Framework v4.0 beta is installed.
08:38:42 0512 The hosting API is up to date.
08:38:42 0512 Calling GetInterface method for the CorRuntimeHost interface.
08:38:42 0512 Success.
08:38:42 0512 Starting CLR...
08:38:42 0512 Success.
08:38:42 0512 Getting the CLR version.
08:38:42 0512 The CLR v4.0.30319 has been initialized successfully.
08:38:42 0512 Creating a new domain setup.
08:38:42 0512 Success.
08:38:42 0512 Getting the add-in directory.
08:38:42 0512 Success. The directory is 'C:Programme_x64MyApp'
08:38:42 0512 The 'shadow copy' is disabled.
08:38:42 0512 Creating a new application domain.
08:38:42 0512 Success.
08:38:42 0512 Getting the base directory for the domain.
08:38:42 0512 Success. The directory is 'C:Programme_x64MyApp'.
08:38:42 0512 Searching for the Add-in Express core library.
08:38:42 0512 Success. The 'AddinExpress.MSO.2005.dll' file is found.
08:38:42 0512 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
08:38:42 0512 Assembly identity is 'AddinExpress.MSO.2005'.
08:38:43 0512 Success.
08:38:43 0512 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
08:38:43 0512 Success.
08:38:43 0512 Calling the managed registration procedure (DISPID = 1610743823).
08:38:43 1100 32 bits. The 'HKCUCLSID{cd028c64-01c8-4b49-932d-242a63a92957}InprocServer32' registry key was created successfully for the 'MyApp.AddinModule' class: C:Programme_x64MyAppdxloader.dll
08:38:43 1100 64 bits. The 'HKCUCLSID{cd028c64-01c8-4b49-932d-242a63a92957}InprocServer32' registry key was created successfully for the 'MyApp.AddinModule' class: C:Programme_x64MyAppdxloader64.dll
08:38:43 0512 Registration success.
08:38:43 0512 The add-in registration process is completed with HRESULT = 0.


Am I missing something? Can I find add somemore logging to pinpoint my issue?

Any help is very appreciated.

Kind Regards

Charles
Posted 04 Mar, 2025 10:43:04 Top
Andrei Smolin


Add-in Express team


Posts: 19095
 Joined: 2006-05-11
Hello Charles,

Uninstall the add-in and unregister the project, then register the project anew - this will let you start Outlook and connect the debugger to OUTLOOK.EXE.

To install the add-in *on the development machine*, unregister the project first and run the installer then.

Note that adxregistrator.log shows you install the add-in to ProgramFiles for a standard user - /privileges=user. This isn't correct: if your add-in is per machine, it should be installed to Program Files with administrative privileges. If, however, your add-in is per-user, it should be installed to the user's profile and not to ProgramFiles as standard users don't have write permissions on the ProgramFiles folders.

Please check sections 'Deploying a per-machine Office extension via an MSI installer' and 'Deploying a per-user Office extension via an MSI installer'; see the PDF file in the folder {Add-in Express}\Docs on your development PC.

Don’t hesitate to contact me again if I can help any further.

Regards from Poland (GMT+1),

Andrei Smolin
Add-in Express Team Leader
Posted 04 Mar, 2025 17:16:32 Top
Charles Lam




Posts: 7
 Joined: 2025-02-21
Hello Andrei,

sorry for may late reponse, there is alot going on. And sadly it didn't work (after following the instructions and/or parts of the documentation) and my last attempt to answer on the forum, ran into an error (probally due to a timeout ) So I will answer short because, currently abit underpressure, to rewrite it:

Basically the issue is only with the old plugin, new demo ones I create work fine. So I just have on remaining Question, is there more logging I can turn on, or is something written in the eventlogs? (since the logs seem fine but I can't select the plugin)?

Since I will have to check our source repo, to see when and how the plugin broken and than work back from there.

In any case thank you very much for always responding so fast and professional

Kind Regards and have a nice day

Charles
Posted 10 Mar, 2025 09:54:08 Top
Andrei Smolin


Add-in Express team


Posts: 19095
 Joined: 2006-05-11
Hello Charles,

There's something I've missed: your adxloader.log reports the registration process while it should describe how your add-in is being loaded by the host Office application. This can be a survivor of an old Add-in Express where we suggested to use adxloader.dll in this way. I strongly recommend that you recheck your add-in project and setup projects against the list of instructions published in these sections of the Add-in Express manual (check out the PDF file in {Add-in Express installation folder}\Docs:
- Deploying a per-user Office extension via an MSI installer
- Deploying a per-machine Office extension via an MSI installer

Specifically, one of the differences I expect you to find is the custom actions. But please make sure you recheck all the steps.

You need to use only one of these sections. To choose the correct one, you need to know whether your add-in is per user or per machine.

Per-user add-ins are installed by the standard user; they register with HKCU; typically, they are installed to the user's profile; no administrative privileges required (admins must use standard user privileges to install such an add-in). Per-machine add-ins install to ProgramFiles, and register with HKLM, and therefore they require administrative privileges at the install/deinstall time.

Regards from Poland (GMT+1),

Andrei Smolin
Add-in Express Team Leader
Posted 10 Mar, 2025 13:17:54 Top