|
|
|
JMP25
Posts: 6
Joined: 2025-02-20
|
Dear Add-In Express team,
I have an issue when I try to debug my add-in for PowerPoint in VS 2022.
I can successfully register the add-in and then start PowerPoint and it will run fine.
This works both in debug as well as release and also for perUser and perMachine.
However, when I have the debug configuration selected and start debugging, my add-in is not loaded when PowerPoint starts.
It is shown as inactive in the add-ins. When I try to activate it in the COM Add-Ins, it will not load.
adxLoader shows "Hash verification failed".
I tried restarting the computer, unregistering + registering many times, I cleaned the project and I manually deleted the bin/Debug and bin/Release folders.
This has been working fine for years, but is now starting to fail after moving to a new development machine.
Any ideas how to solve this?
----
Add-in Express Loader Log File: 02/20/2025 09:06:40:920
Startup directory: C:\Users\UserName\source\repos\XXX\XXX\bin\Debug\
Loader version: 10.2.4714.0
Operating System: Microsoft Windows 10 Professional (build 26100), 64-bit
Process Owner: Administrator
Command Line: "C:\Program Files\Microsoft Office\root\Office16\POWERPNT.EXE"
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): On
------------------------------------------------------------------------
09:06:40:928 3756 4308 Start.
09:06:40:928 3756 4308 The host's version is 16.0.18429.20158
09:06:40:928 3756 4308 Creating a new instance of the add-in loader.
09:06:40:928 3756 4308 Loading mscoree.dll
09:06:40:928 3756 4308 INFO: Assembly codebase - C:\Users\UserName\source\repos\XXX\XXX\bin\Debug\XXX.dll.
09:06:40:928 3756 4308 INFO: Assembly version - 2.21.22.0.
09:06:40:928 3756 4308 Success.
09:06:40:928 3756 4308 Loading the configuration from the system registry.
09:06:40:928 3756 4308 Getting the latest CLR version.
09:06:40:928 3756 4308 The latest CLR version is 'v4.0.30319'.
09:06:40:928 3756 4308 The configuration has been loaded successfully.
09:06:40:928 3756 4308 Runtime version: v4.0.30319.
09:06:40:928 3756 4308 Assembly name: XXX, PublicKeyToken=XXXX.
09:06:40:928 3756 4308 Class name: XXX.AddinModule.
09:06:40:928 3756 4308 Registry key: CLSID\{XXX}.
09:06:40:928 3756 4308 Attempting to create a new instance of the managed add-in class: CLR - v4.0.30319
09:06:40:928 3756 4308 Loading CLR: v4.0.30319.
09:06:40:928 3756 4308 Calling CLRCreateInstance method.
09:06:40:928 3756 4308 Success.
09:06:40:928 3756 4308 Calling GetRuntime method.
09:06:40:928 3756 4308 Success.
09:06:40:928 3756 4308 Checking if the hosting API of .NET Framework v4.0 beta is installed.
09:06:41:042 3756 4308 The hosting API is up to date.
09:06:41:042 3756 4308 Calling SetDefaultStartupFlags method.
09:06:41:042 3756 4308 Success.
09:06:41:042 3756 4308 Calling GetInterface method for the CorRuntimeHost interface.
09:06:41:042 3756 4308 Success.
09:06:41:042 3756 4308 Starting CLR...
09:06:41:042 3756 4308 Success.
09:06:41:042 3756 4308 Getting the CLR version.
09:06:41:042 3756 4308 The CLR v4.0.30319 has been initialized successfully.
09:06:41:125 3756 4308 Hash verification failed |
|
|
Posted 20 Feb, 2025 08:41:42
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19177
Joined: 2006-05-11
|
Hello,
Make sure adxloader.dll and adxloader64.dll are not rewritten after you published it. BTW, is the loader signed? Is the certificate valid?
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 20 Feb, 2025 16:23:12
|
|
Top
|
|
|
JMP25
Posts: 6
Joined: 2025-02-20
|
Hi Andrei,
both loaders (adxloader and adxloader64) are signed and the certificate is valid.
I am not sure what you mean with this:
"Make sure adxloader.dll and adxloader64.dll are not rewritten after you published it."
When I register the add-in and start PowerPoint, the add-in loads and everything is fine.
But when I then start debugging, I get the hash verification failed.
I can see start when I start to debug, a build is triggered and the loaders are signed again.
When i look at the files in bin/debug, they seem to have the right signature.
best regards,
JMP |
|
|
Posted 20 Feb, 2025 17:19:53
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19177
Joined: 2006-05-11
|
Hello JMP,
Oh, I see. I assume you register the add-in project to start debugging it. Anyway, it looks like bin\Debug contains adxloader.dll and adxloader64.dll that are different from that (those) loading the add-in when you simply start the host application.
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 21 Feb, 2025 11:17:31
|
|
Top
|
|
|
Pierre Alain Carrier
Posts: 50
Joined: 2011-12-22
|
I have the same problem. If I register the add-in and run Excel, everything works fine. As soon as I try debugging, I get "Hash verification failed".
I noticed that, when looking at the output window, if I'm registering, it will sign both adxloader, the manifest and the add-in, but when debugging, it does not sign the manifest, only the three dll. |
|
|
Posted 25 Apr, 2025 20:35:29
|
|
Top
|
|
|
Pierre Alain Carrier
Posts: 50
Joined: 2011-12-22
|
I figured it out. If the code is not touched (no change), the manifest file does not get signed. If I modify something, then it gets signed.
In any case, I will disable the signing and only sign before deployment. |
|
|
Posted 25 Apr, 2025 20:49:30
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19177
Joined: 2006-05-11
|
Hello Pierre,
Thank you for letting us know!
Regards from Poland (GMT+2),
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 28 Apr, 2025 09:48:02
|
|
Top
|
|
Forums
Topics
Search
Help
Login
Register