Hi and welcome to our forums, I have tested the scenario but I cannot replicate the behavior. Can you please tell us what version of Advanced Installer are you currently using? Also, can you please try removing your certificate from your Yubikey USB dongle, then removing it from your Windows machine...
Hi Alex, We were able to replicate sporadically the same Key Vault signing error on our side too. Most likely the signing error is caused by the Microsoft's Azure Key Vault servers that seems to be unresponsiveness sometimes. We worked on an improvement (we retry the Key Vault signing several times ...
Hi, I am afraid I really cannot say what exactly goes wrong when your application is packaged into an MSIX. You ca either try to debug your MSIX packaged app code or you can try to run our “TraceApp” feature in Advanced Installer (available only in the Architect edition). If you do now own an Archit...
Hi Zsolt, Looking over your sent log file it seems there is a problem with the creation of the web application pool. Can you please send us the .aip (project file) by email at support at advancedinstaller dot com so we can investigate its settings and run a few tests on our side too? All the best, D...
Hi, I can confirm you the workaround solution you were thinking of is the correct one. And this is just because our built-in "Call method from .Net assembly custom action" type does not support targeting both architectures ("Any CPU') of .NET Runtime at once. It can either target the ...
Hi, Let's assume you have built a .Net assembly custom action DLL that can be ran by both architectures of .NET Runtime (Any CPU build configuration). screen1.jpg Now you may want the above custom action code be executed at install time by your setup package regardless the .NET Runtime architecture ...
Hi, Thank you for your feedback on this! We are currently working as we speak to some improvement that we hope will avoid such issues. In the meantime, as a workaround solution you can try indeed to use the "azuresigntool.exe" tool to sign your setup project. This tool can be install using...
Hi, Unfortunately these seems to be false positive detections of Windows Defender. The quickest action you can implement will be to add a Defender exclusion on the output folder where your setup project is built. The best practice when such false positive detection occurs is to submit a report to Wi...