The instructions to which you refer do not, for example, discuss the post-build event that the VS Windows installer project performs with adxpatch.exe. The automated conversion wizard results in much less understandable settings than a methodical approach.

The VS Windows Installer always correctly installs the add-in, but I have other unrelated issues with it getting confused and delivering the wrong transient dependencies that make me want to port it to a more powerful MSI building solution. Thanks for the prompt reply but I am working with one of those Advanced Installer guys and we cannot seem to get the calls to adxregistrator.exe to result in my add in being registered from an msi based on Advanced Installer. Any assistance appreciated and you can also reach out directly to Dan as I'm not their only customer using ADX (obviously).Īlso where might we expect the log file to go on a failed registration? None of this is resulting in a properly installed add-in. install='' /privileges=user /generateLogFile=trueĮven though we don't understand what it does, we also added the following post-build command:Ĭ:Program Files (x86)Add-in ExpressAdd-in Express for. uninstall='' /privileges=user /generateLogFile=false Here are the commands we have defined that are not working: What precise incantation at the command line do we need at each stage, so I can try to do it locally? 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. I am working with Dan at We are not able following the instructions at XXXX to get an installer that successfully registers my add-in to Office.

Advanced installer express