|
Bruno D
Posts: 9
Joined: 2023-05-05
|
I have an issue registering my Addin, it seems like some temp files / registry files get corrupted after some registration / unregistration of my Addin.
I have my debug project
/bin/Debug/Word Tools.dll (AnyCPU)
/bin/Debug/adxloader64.dll
/bin/Debug/adxloader64.dll.manifest
...
And also an installed project
/Program Files/.../Word Tools.dll
/Program Files/.../adxloader64.dll
/Program Files/.../adxloader64.dll.manifest
/Program Files/.../adxregistrator.exe
The manifest is as follow:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<assemblyIdentity name="Word Tools, PublicKeyToken=null" />
<loaderSettings generateLogFile="true" privileges="administrator">
</loaderSettings>
</configuration>
When I do development, when I happen to remove the addin from the COM list directly in word, to then add my debug dll using /bin/Debug/adxloader64.dll
But it seems to have broke something, after I removed it, I can't register anything anymore. When I use the adxregistrator.exe,
Add-in Express Registrator Log File: 08/06/2024 13:16:35
Installation directory: C:\Program Files\...\Word Tools\
Registrator version: 10.2.4714.0
Operating System: Microsoft Windows 10 Professional (build 19045), 64-bit
Process Owner: Administrator
Command Line: "C:\Program Files\...\Word Tools\adxregistrator.exe" "/install="C:\Program Files\...\Word Tools\Word Tools.dll" /privileges=admin"
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): On
--------------------------------------------------------------
13:16:35 0584 Starting the add-in registration process.
13:16:35 0584 Loading mscoree.dll
13:16:35 0584 Success.
13:16:35 0584 .NET Framework installation directory:
13:16:35 0584 The latest version of .NET Framework: 'v4.0.30319'
13:16:35 0584 Loading CLR: v4.0.30319.
13:16:35 0584 Calling CLRCreateInstance method.
13:16:35 0584 Success.
13:16:35 0584 Calling GetRuntime method.
13:16:35 0584 Success.
13:16:35 0584 Checking if the hosting API of .NET Framework v4.0 beta is installed.
13:16:35 0584 The hosting API is up to date.
13:16:35 0584 Calling GetInterface method for the CorRuntimeHost interface.
13:16:35 0584 Success.
13:16:35 0584 Starting CLR...
13:16:35 0584 Success.
13:16:35 0584 Getting the CLR version.
13:16:35 0584 The CLR v4.0.30319 has been initialized successfully.
13:16:35 0584 Creating a new domain setup.
13:16:35 0584 Success.
13:16:35 0584 The 'shadow copy' is disabled.
13:16:35 0584 Creating a new application domain.
13:16:35 0584 Success.
13:16:35 0584 Getting the base directory for the domain.
13:16:35 0584 Success. The directory is 'C:\Program Files\...\Word Tools\'.
13:16:35 0584 Searching for the Add-in Express core library.
13:16:35 0584 Success. The 'AddinExpress.MSO.2005.dll' file is found.
13:16:35 0584 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
13:16:35 0584 Assembly identity is 'AddinExpress.MSO.2005'.
13:16:35 0584 Success.
13:16:35 0584 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
13:16:35 0584 Success.
13:16:35 0584 Calling the managed registration procedure (DISPID = 1610743823).
13:16:35 0584 Registration success.
13:16:35 0584 The add-in registration process is completed with HRESULT = 0.
It appears to have succeeded, but the addin will not be loaded.
If I try to load adxloader64.dll manually, I will get the following message: "The system cannot find the file specified". I don't think it's coming from my addin, I tried putting a dummy messagebox in the ADXAddinModule implementation constructor and it's not called.
Also, if I install it on any other computer, it will install properly without issue, until I do that manual removal manipulation. How can I fix this? I've tried clearing up %temp%, but that did not work.
Thanks |
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Bruno,
Installing your add-in and registering your add-in project creates a mess in the registry. Unregister your project, uninstall your add-in, make sure the host Office application doesn't show any traces of your add-in, close the host application, register your project and debug it.
Bruno D writes:
it will install properly without issue, until I do that manual removal manipulation
Why would you need to remove the add-in manually? What are the exact steps you follow?
Regards from Poland (GMT+2),
Andrei Smolin
Add-in Express Team Leader |
|
|
Bruno D
Posts: 9
Joined: 2023-05-05
|
Hello Andrei,
Indeed, there is no trace of my application in neither "Active Application Add-ins" nor "Inactive Application Add-ins" in Word "Add-ins" panel (File>Options>Add-ins>COM Add-ins). Even though adxregistrator.log says the installation has been successful, it is not added under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Word\Addins (Not in HKCU either). Which is odd...
The manipulation is something I've been doing before, but somehow it seems to go wrong now. (Both of my dev machine are in this state where I'm unable to install my add-in anymore). The reason I was removing the addon manually is because I didn't necessarily want to uninstall the application (In Add and remove programs) to be able to debug it, so I removed the installed add-in in Word (File>Options>Add-ins>COM Add-ins>Remove) to then add the one in my bin/Debug/ folder so it points where my currently developed dll is compiled, to eventually point back to the installed version after shipping.
Also may be worth mentioning that when I install, I always run the registration like this:
"C:\Program Files\...\Word Tools\adxregistrator.exe" "/uninstall="C:\Program Files\...\Word Tools\Word Tools.dll" /privileges=admin
"C:\Program Files\...\Word Tools\adxregistrator.exe" "/install="C:\Program Files\...\Word Tools\Word Tools.dll" /privileges=admin
To reactivate it, in case it is already registered |
|
|
Bruno D
Posts: 9
Joined: 2023-05-05
|
|
Would it be possible to get access to adxloader64.dll code? I want to understand what's going :/ |
|
|
Andrei Smolin
Add-in Express team
Posts: 19011
Joined: 2006-05-11
|
Hello Bruno,
First off, uninstall the add-in and unregister your project from the Visual Studio IDE. Then search the registry to remove COM registrations related to your add-in. Note that the add-in is registered in the 32-bit and 64-bit registry.
You can target the Project Output of your add-in project to the add-in installation folder.
The source code of adxloader/adxloader64 is only accessible on request for the Premium subscription.
Regards from Poland (GMT+2),
Andrei Smolin
Add-in Express Team Leader |
|
Forums
Topics
Search
Help
Login
Register