Problem using Advanced Installer

[Halliessed]

I am working with Dan at support@advancedinstaller.com. We are not able following the instructions at XXXX to get an installer that successfully registers my add-in to Office. We followed the instructions there to the T, and added a post-build step that we THINK replicates what the generated Windows setup project does, but still it does not work.

What precise incantation at the command line do we need at each stage, so I can try to do it locally?geometry dash lite

Here are the commands we have defined that are not working:

On Uninstall:

Code: Select all

[#adxregistrator.exe] /uninstall="[#Accelerate365.dll]" /privileges=user /generateLogFile=false 

On Install:

Code: Select all

[#adxregistrator.exe] /install="[#Accelerate365.dll]" /privileges=user /generateLogFile=true 

On Rollback:

[#adxregistrator.exe] /uninstall="[#Accelerate365.dll]" /privileges=user /generateLogFile=false

Even though we don't understand what it does, we also added the following post-build command:

Code: Select all

C:Program Files (x86)Add-in ExpressAdd-in Express for .NETBindxpatch.exe "[|AI_BUILD_OUTPUT_FOLDER]Accelerate365-Setup.msi" /UAC=Off /RunActionsAsInvoker=true 

None of this is resulting in a properly installed add-in. Any assistance appreciated and you can also reach out directly to Dan as I'm not their only customer using ADX (obviously).

Also where might we expect the log file to go on a failed registration?

[Catalin]

Hello and welcome to our forums,

First of all, if you have a ticket already opened with one of our support members, please try to avoid replicating the same ticket on the forum as well, as the same members from our team work both on forum and email.

Now, regarding your issues, the first thing to note here is that adxregistrator.exe is a third party tool and is not proprietary to us.

What you would need to do is the following:

1. add adxregistrator.exe and all its' dependencies in the "Application Folder" from the "Files and Folders" page.

2. go to "Custom Actions" page and add a "Launch installed file" custom action, something like this:

Screenshot_64.png (9.09KiB)Viewed 2863 times

3. the custom action should be added after the "Add resources" action group.

4. the custom action should have its' "Execution time" set to "When the system is being modified (deferred)" and the "Run under the LocalSystem account with full privileges (no impersonation)" option also checked - this will ensure the custom action runs elevated and has enough privileges to register the dll.

Regarding the log file in case of a failed registration, I'm afraid I can't really tell because, as I've previously explained, that is a third party tool.

Best regards,
Catalin