Yeah sure, I am fine following up through existing mail thread.
It's just that we were not getting timely responses, and this is something blocking the release, hence raised as ticket in forum as well.
We have created custom action which will call a method from the .dll file (CustomeActionInstaller.CA.dll) to execute custom logic written under that. Inside the CustomeActionInstaller.CA.dll, the method will make a use of Session variable to get and set data as shown below 1.png
I created Word add-in by selecting project template in VS 2019. I have followed mentioned steps to create aip file for that word add-in, but I do not see any projects getting listed when I select solution. I have attached screenshots as reference. Any help would be appreciated.
We re-ordered custom actions and made sure that password setup and start services custom action runs at the end of execution.
After above changes, we were able to fix this issue.
Scenario is, assume we have generated an EXE which has version 1.0.0. Now, we have generated patch (which will be versioned as 1.0.1 and will be targeting 1.0.0). Users are able to install patch successfully.
Now, we have generated another patch targeting version 1.0.1 and will be ...
We have an application that was build for 32 bit versions and gets installed at C:\Program Files (x86)\... location. We are using Advanced Installer 16.5 version to build EXE. Now, we have upgraded our application to build for 64 bit versions and it gets installed at C:\Program Files ...
For now, I have skipped RegistryCleanUp custom action in case of Patch scenario as suggested option did not worked. But now, I am running into different issues.
We are using custom actions to set user password for services those are being installed / updated during Install / patch of exe. Image1 ...
I tried above option and it did not worked. I also added another custom action with suggested configuration and added a condition to run it only for Patch scenario but still no luck. So at the end, I had to skip this custom action for Patch scenario as of now.
For our project, we are using Advanced Installer 16.5 to generate installation exe from AIP file. We are also using same AIP file to generate patch. Install, Uninstall and Patch runs under Admin privileges.
In AIP, we have written a custom action, which does some registry clean-up. I have attached ...
FOLLOW US
Get the latest news in Application Packaging