Advanced Installer Community

sasha

Hello, thanks for looking at this issue. I have converted our installer project from producing an .msi file to produce an .exe. The main reason being the UAC prompt that is presented at the time of the launch, rather than later. That solves a number of inconvenient issues for us. Now, what I observe...

sasha

Thank you!

sasha

Thanks! I did try online Base64 decoder and it returned garbage. Should've tried more.

Still, I implore you to stop the encoding, as it makes code reviews very difficult.

sasha

Hello! The problem with the encoded state of the scripts is that it's impossible to perform reviews on them. I doubt very much users manually modifying the scripts in the .aip file is such a huge problem. The inability to perform proper source/version control via code reviews is a much bigger proble...

sasha

I understand. My post was more of an alert the issue is still happening out in the field. If I find out more information on reproducing it, I will share it.

sasha

Unfortunately, I don't think I can do that. I personally have never seen it, but our QA see the issue occasionally. On the same system it happens So, coming up with a sample project is unlikely... Here is what the QA reported: files are copied or moved to C:\AI_RecycleBin\ folder under a unique fold...

sasha

Well our QA just alerted me to this issue happening when using AI 20.7.1.

sasha

Thanks for the reply, Catalin. The issue does seem to be machine-specific. I cannot reproduce this at-will. The same MSI will work fine elsewhere, but fail on a 'bad' system. The 'run from' is selected to be the temporary folder in the AI Powershell script options. The links I included possible expl...

sasha

Hello! Our (un)installer runs a few Powershell scripts. They all are running from the temp folder (as specified in the Powershell execution options). Unfortunately, on some systems, the invocation of the scrip generates the following error: > MSI (c) (44:90) [18:40:33:647]: Invoking remote custom ac...

sasha

Is there any other option to send the sample project?
Thanks!

sasha

The receiving email server refused to accept the email with the .zip file attached:

Error: 550 5.0.350 One or more of the attachments in your email is of a file type that is NOT allowed by the recipient's organization.
Message rejected by: CY8PR11MB7135.namprd11.prod.outlook.com

sasha

Sample project emailed.

sasha

Thanks for the reply, Catalin. I will try to come up with something ${L_SMILIES_SMILE}$

sasha

I have now also noticed that some of the hidden properties are logged in a clear text. Indeed, they are passed as action data to a custom action (a VB script). In the log file they are present like this: PROPERTY CHANGE: Adding XXX_Propertyproperty. Its value is YYY_clear_text. I've followed the sug...

sasha

Having this capability would be extremely nice. A single .msi targeting x64 and ARM64 is becoming a hot requirement, at least for me. A part of our installation is x64, even on the ARM64. And we use custom actions to call into out x64 DLLs during uninstall, etc. As is, the custom action 'call functi...

Suggested Articles

User Guide

Videos

Search found 25 matches

ExitDialog is executed twice

Re: AI_DATA_SETTER encoding

Re: AI_DATA_SETTER encoding

Re: AI_DATA_SETTER encoding

Re: AI_Recyclebin Folder on all drives

Re: AI_Recyclebin Folder on all drives

Re: AI_Recyclebin Folder on all drives

Re: An issue with running PowerShell scripts

An issue with running PowerShell scripts

Re: Hidden properties logged in plain text when passed as CustomActionData

Re: Hidden properties logged in plain text when passed as CustomActionData

Re: Hidden properties logged in plain text when passed as CustomActionData

Re: Hidden properties logged in plain text when passed as CustomActionData

Re: Hidden properties logged in plain text when passed as CustomActionData

Re: Single installer for x86/x64/ARM64

Caphyon Products

Company

Product

Resources

Free Tools

Connect