Hi, Our dev team released a fix for this issue. From now on, when you have concurrent pipelines building an Advanced Installer setup project you can skip the license cleanup on post-build task. To do so you should just define a pipeline variable like this: Name: advancedinstaller.cleanup Value: fals...
Hi, To achieve what you want you should simply copy the content of your .aic file (excluding its first line: ;aic) and add the commands in the "Command Line Arguments" section of your DevOps build task. For instance: SetVersion 1.2 SetProperty TESTPROP="TestValue" Save screen.jpg...
Hi Zsolt, I am afraid the sent log file does not contain any useful info regarding the error cause. It seems the installation just fails to enable the Windows Features and/or Server Roles you configured into your setup project. Could you please try your customer to run the setup package with a debug...
Thank you for sharing your feedback. We will try to add some improvements in regards to the Nuget packages and app dependencies refresh in the future, thank you for bringing this to our attention.
When this improvement is out we will update this forum thread.
Hi Gabriel, Also, as another possible workaround solution just add a "PowerShell Script" task (just after "Build Advanced Installer" task) with the following code: Write-Host "##vso[task.setvariable variable=advinst.cleanup;]" Check attached screenshot. image.png This s...
Hi Gabriel, I have talked with our dev team about this limitation and we will try to add an improvement in this regard. We will try to make available a pipeline variable you could define in Azure DevOps and when such variable is set the license file cleanup on post-job task to be skipped. When such ...
Hi Gabriel, Indeed this is our current default design. The License file is deleted on post-job task. As a workaround, yes please use a "Advanced Installer Build" task (instead of a batch to call Advanced Installer) and specify your license key in the "Advanced Installer Build" ta...
Unfortunately we do not have support for any of your queries. However, I have forwarded your feedback to our dev team and maybe we will consider these improvements in the future.
Hi Hans, This behavior is generated by the "Check launch conditions before searching for prerequisites" option from "Prerequisites" page. Could you please uncheck this option and then rebuild and test again you scenario? screen.jpg When this option is checked, what actually happe...
Analyzing your sent log file it seems the installation fialure of the log you have sent is caused by a failure of one of your custom action: SetWebAccessAuth
Could you try to debug your custom action code and make sure it returns an exit code of 0 (success)?
Hi Jaime, Understood. To avoid this corner case issue please just create the updates configuration project and build the updates configuration file using the current version of your setup. Then host it on your updates web sever. In this way you will get ab application is up to date message when chec...